Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 31
  1. #11
    Newbie
    Join Date
    May 2010
    Posts
    11

    Default

    Ok everyone... a little more information....

    In looking through the Postgres log files... it is completely filled with the following line:

    Code:
    CDT FATAL:  database "root" does not exist

  2. #12
    Untangle Junkie dmorris's Avatar
    Join Date
    Nov 2006
    Location
    San Carlos, CA
    Posts
    17,486

    Default

    you can ignore that - it doesn't mean anything
    Attention: Support and help on the Untangle Forums is provided by volunteers and community members like yourself.
    If you need Untangle support please call or email support@untangle.com

  3. #13
    Newbie
    Join Date
    May 2010
    Posts
    11

    Default

    Ok, a little more digging....

    In experimenting, I have removed all modules except web filtering and reports. Upon executing the process.py script I see the following error in the postgres log. (I believe I probably already posted this as part of a previous log, but just incase anybody missed it.)

    Code:
    2010-05-20 15:17:55 CDT ERROR:  relation "reports.n_http_events" does not exist
    2010-05-20 15:17:55 CDT STATEMENT:  UPDATE reports.n_http_events
    	SET wf_untangle_action = action,
    	  wf_untangle_reason = reason,
    	  wf_untangle_category = category
    	FROM events.n_webfilter_evt_blk
    	WHERE reports.n_http_events.time_stamp >= '2010-05-19'
    	  AND reports.n_http_events.time_stamp < '2010-05-20'
    	  AND events.n_webfilter_evt_blk.vendor_name = 'untangle'
    	  AND reports.n_http_events.request_id = events.n_webfilter_evt_blk.request_id

  4. #14
    Untangle Junkie dmorris's Avatar
    Join Date
    Nov 2006
    Location
    San Carlos, CA
    Posts
    17,486

    Default

    can you run 'ucli instances' and post the output? is web filtering working?


    also try this:
    run:
    echo 'drop schema reports cascade' | psql -U postgres uvm
    then run process.py by hand (will take a while)

    if there is still a problem post the entire reporter.log somewhere so we can see the entire thing.
    Attention: Support and help on the Untangle Forums is provided by volunteers and community members like yourself.
    If you need Untangle support please call or email support@untangle.com

  5. #15
    Newbie
    Join Date
    May 2010
    Posts
    11

    Default

    Here is the output of the first command:

    Code:
    ~ # ucli instances                                                                                                                                                [root @ untangle]
    2	untangle-casing-ftp      	null	RUNNING
    4	untangle-casing-http     	null	RUNNING
    5	untangle-casing-mail     	null	INITIALIZED
    33	untangle-node-webfilter  	Policy(default: Default Rack)	RUNNING
    17	untangle-node-license    	null	RUNNING
    1	untangle-node-router     	null	RUNNING
    34	untangle-node-adconnector	null	RUNNING
    36	untangle-node-reporting  	null	RUNNING
    And here is a link to the reporter.log file: reporter.log

    Your help is greatly appreciated. Thank you.

  6. #16
    Newbie
    Join Date
    May 2010
    Posts
    11

    Default

    Nothing standing out in the logs?

  7. #17
    Newbie
    Join Date
    Dec 2009
    Posts
    8

    Default

    Good day,

    We experiencing exactly the same issue here, our server Untangle 7.3 RC3 is in production for over 48 hours, still no reports.

    /var/log/uvm # ucli instances [root @ u01]
    2 untangle-casing-ftp null RUNNING
    4 untangle-casing-http null RUNNING
    10 untangle-casing-mail null RUNNING
    11 untangle-node-spamassassin Policy(default: Default Rack) INITIALIZED
    3 untangle-node-webfilter Policy(default: Default Rack) RUNNING
    9 untangle-node-clam Policy(default: Default Rack) RUNNING
    8 untangle-node-protofilter Policy(default: Default Rack) RUNNING
    15 untangle-node-license null RUNNING
    1 untangle-node-router null RUNNING
    16 untangle-node-policy null RUNNING
    17 untangle-node-adconnector null RUNNING
    5 untangle-node-shield null RUNNING
    6 untangle-node-reporting null RUNNING
    and you if you trying to check reports online, no reports available notice is shown.

    reporter.log
    2010-05-26 15:30:12 [sql_helper] DEBUG: init_engine (reports/engine:395) took 106.554 ms
    2010-05-27 01:27:27 [__main__] DEBUG: day_of_week: 5
    2010-05-27 01:27:27 [__main__] WARNING: settings_id: 909855
    2010-05-27 01:27:27 [__main__] INFO: Generating reports for the following lengths: [1]
    2010-05-27 01:27:27 [__main__] INFO: using locale: en
    2010-05-27 01:27:28 [__main__] INFO: db_settings: {'email_detail': 0, 'db_retention': 21, 'attachment_size_limit': 10L, 'file_retention': 60}
    2010-05-27 01:27:28 [sql_helper] DEBUG: fix_hierarchy (reports/engine:435) took 0.105 ms
    2010-05-27 01:27:28 [sql_helper] DEBUG: init_engine (reports/engine:395) took 70.122 ms
    2010-05-27 01:27:28 [engine] DEBUG: doing setup for: untangle-vm (2010-05-26 00:00:00.00 -> 2010-05-27 00:00:00.00)
    2010-05-27 01:27:28 [sql_helper] DEBUG: __do_housekeeping (reports/node/untangle_vm:376) took 450.002 ms
    2010-05-27 01:27:28 [sql_helper] DEBUG: __generate_abs_leases (reports/node/untangle_vm:428) took 15.602 ms
    2010-05-27 01:27:28 [sql_helper] DEBUG: __generate_relative_leases (reports/node/untangle_vm:442) took 0.695 ms
    2010-05-27 01:27:28 [sql_helper] DEBUG: __generate_static_leases (reports/node/untangle_vm:451) took 0.844 ms
    2010-05-27 01:27:28 [sql_helper] DEBUG: __generate_manual_map (reports/node/untangle_vm:478) took 24.760 ms
    2010-05-27 01:27:28 [sql_helper] DEBUG: __write_leases (reports/node/untangle_vm:404) took 0.142 ms
    2010-05-27 01:27:28 [sql_helper] DEBUG: __generate_address_map (reports/node/untangle_vm:361) took 494.268 ms
    2010-05-27 01:27:29 [sql_helper] DEBUG: Created partitioned table for reports.n_admin_logins ('2010-05-26' -> '2010-05-27')
    2010-05-27 01:27:29 [sql_helper] DEBUG: __create_n_admin_logins (reports/node/untangle_vm:100) took 273.082 ms
    2010-05-27 01:27:29 [sql_helper] DEBUG: Created partitioned table for reports.sessions ('2010-05-26' -> '2010-05-27')
    2010-05-27 01:27:44 [sql_helper] DEBUG: __make_sessions_table (reports/node/untangle_vm:252) took 15625.887 ms
    2010-05-27 01:27:45 [sql_helper] DEBUG: Created partitioned table for reports.session_counts ('2010-05-26' -> '2010-05-27')
    2010-05-27 01:27:48 [sql_helper] DEBUG: __make_session_counts_table (reports/node/untangle_vm:316) took 3754.530 ms
    2010-05-27 01:27:48 [engine] DEBUG: registering fact table: 'reports.session_totals': '<reports.engine.FactTable instance at 0x1d9a950>'
    2010-05-27 01:27:48 [sql_helper] DEBUG: __get_branded_name (reports/node/untangle_vm:86) took 0.293 ms
    2010-05-27 01:27:48 [sql_helper] DEBUG: setup (reports/node/untangle_vm:60) took 20149.458 ms
    2010-05-27 01:27:48 [engine] DEBUG: doing setup for: untangle-casing-http (2010-05-26 00:00:00.00 -> 2010-05-27 00:00:00.00)
    2010-05-27 01:27:48 [sql_helper] WARNING: could not access database, getting new connection

    Traceback (most recent call last):
    File "/usr/lib/python2.5/reports/sql_helper.py", line 75, in get_connection
    curs.execute("SELECT 1")
    ProgrammingError: ERROR: current transaction is aborted, commands ignored until end of transaction block

    SELECT 1
    2010-05-27 01:27:48 [engine] WARNING: could not setup for: untangle-casing-http
    Traceback (most recent call last):
    File "/usr/lib/python2.5/reports/engine.py", line 415, in setup
    node.setup(start_date, end_date)
    File "/usr/lib/python2.5/reports/sql_helper.py", line 45, in wrapper
    res = func(*arg)
    File "/usr/lib/python2.5/reports/node/untangle_casing_http.py", line 36, in setup
    self.__create_n_http_events(start_date, end_date)
    File "/usr/lib/python2.5/reports/sql_helper.py", line 45, in wrapper
    res = func(*arg)
    File "/usr/lib/python2.5/reports/node/untangle_casing_http.py", line 72, in __create_n_http_events
    'time_stamp', start_date, end_date)
    File "/usr/lib/python2.5/reports/sql_helper.py", line 151, in create_partitioned_table
    run_sql(table_ddl)
    File "/usr/lib/python2.5/reports/sql_helper.py", line 128, in run_sql
    connection.rollback()
    InterfaceError: already closed

    2010-05-27 01:27:48 [engine] WARNING: could not setup for: untangle-node-webfilter
    Traceback (most recent call last):
    File "/usr/lib/python2.5/reports/engine.py", line 415, in setup
    node.setup(start_date, end_date)
    File "/usr/lib/python2.5/reports/sql_helper.py", line 45, in wrapper
    res = func(*arg)
    File "/usr/lib/python2.5/reports/node/untangle_base_webfilter.py", line 66, in setup
    self.__update_n_http_events(start_date, end_date)
    File "/usr/lib/python2.5/reports/sql_helper.py", line 45, in wrapper
    res = func(*arg)
    File "/usr/lib/python2.5/reports/node/untangle_base_webfilter.py", line 166, in __update_n_http_events
    raise e
    ProgrammingError: ERROR: relation "reports.n_http_events" does not exist

    UPDATE reports.n_http_events
    SET wf_untangle_action = action,
    wf_untangle_reason = reason,
    wf_untangle_category = category
    FROM events.n_webfilter_evt_blk
    WHERE reports.n_http_events.time_stamp >= '2010-05-26'
    AND reports.n_http_events.time_stamp < '2010-05-27'
    AND events.n_webfilter_evt_blk.vendor_name = 'untangle'
    AND reports.n_http_events.request_id = events.n_webfilter_evt_blk.request_id
    2010-05-27 01:27:48 [engine] DEBUG: doing setup for: untangle-node-protofilter (2010-05-26 00:00:00.00 -> 2010-05-27 00:00:00.00)
    2010-05-27 01:27:48 [engine] WARNING: could not setup for: untangle-node-protofilter
    Traceback (most recent call last):
    File "/usr/lib/python2.5/reports/engine.py", line 415, in setup
    node.setup(start_date, end_date)
    File "/usr/lib/python2.5/reports/node/untangle_node_protofilter.py", line 55, in setup
    self.__update_sessions(start_date, end_date)
    File "/usr/lib/python2.5/reports/sql_helper.py", line 45, in wrapper
    res = func(*arg)
    File "/usr/lib/python2.5/reports/node/untangle_node_protofilter.py", line 128, in __update_sessions
    raise e
    ProgrammingError: ERROR: column "pf_protocol" of relation "sessions" does not exist
    LINE 2: SET pf_protocol = protocol,
    and so on, i've done re-install of that module, but no luck.

    Any suggestions, to fix it on production server?

  8. #18
    Newbie
    Join Date
    Oct 2009
    Location
    Warren, Ohio
    Posts
    5

    Default Same issue here

    We seem to be having the same issue here. No reports have been generated since Sunday (the upgrade to 7.3 happened Monday morning)
    ucli instances
    2 untangle-casing-ftp null RUNNING
    4 untangle-casing-http null RUNNING
    7 untangle-casing-mail null RUNNING
    8 untangle-node-spyware Policy(default: Default Rack) RUNNING
    3 untangle-node-webfilter Policy(default: Default Rack) RUNNING
    6 untangle-node-clam Policy(default: Default Rack) RUNNING
    9 untangle-node-license null RUNNING
    1 untangle-node-router null RUNNING
    15 untangle-node-reporting null RUNNING
    reporter.log
    2010-05-28 01:00:13 [__main__] DEBUG: day_of_week: 6
    2010-05-28 01:00:13 [__main__] WARNING: settings_id: 11536077
    2010-05-28 01:00:13 [__main__] INFO: Generating reports for the following lengths: [1]
    2010-05-28 01:00:13 [__main__] INFO: using locale: en
    2010-05-28 01:00:14 [__main__] INFO: db_settings: {'email_detail': 0, 'db_retention': 30, 'attachment_size_limit': 10L, 'file_retention': 30}
    2010-05-28 01:00:14 [sql_helper] DEBUG: fix_hierarchy (reports/engine:435) took 2.764 ms
    2010-05-28 01:00:14 [sql_helper] DEBUG: init_engine (reports/engine:395) took 289.444 ms
    2010-05-28 01:00:14 [engine] DEBUG: doing setup for: untangle-vm (2010-05-27 00:00:00.00 -> 2010-05-28 00:00:00.00)
    2010-05-28 01:00:14 [sql_helper] DEBUG: __do_housekeeping (reports/node/untangle_vm:376) took 452.149 ms
    2010-05-28 01:00:14 [sql_helper] DEBUG: __generate_abs_leases (reports/node/untangle_vm:428) took 4.525 ms
    2010-05-28 01:00:14 [sql_helper] DEBUG: __generate_relative_leases (reports/node/untangle_vm:442) took 2.070 ms
    2010-05-28 01:00:14 [sql_helper] DEBUG: __generate_static_leases (reports/node/untangle_vm:451) took 2.783 ms
    2010-05-28 01:00:15 [sql_helper] DEBUG: __generate_manual_map (reports/node/untangle_vm:478) took 553.973 ms
    2010-05-28 01:00:15 [sql_helper] DEBUG: __write_leases (reports/node/untangle_vm:404) took 0.618 ms
    2010-05-28 01:00:15 [sql_helper] DEBUG: __generate_address_map (reports/node/untangle_vm:361) took 1022.219 ms
    2010-05-28 01:00:15 [sql_helper] DEBUG: Created partitioned table for reports.n_admin_logins ('2010-05-27' -> '2010-05-28')
    2010-05-28 01:00:15 [sql_helper] DEBUG: __create_n_admin_logins (reports/node/untangle_vm:100) took 275.748 ms
    2010-05-28 01:00:15 [sql_helper] DEBUG: Created partitioned table for reports.sessions ('2010-05-27' -> '2010-05-28')
    2010-05-28 01:00:17 [sql_helper] DEBUG: __make_sessions_table (reports/node/untangle_vm:252) took 1843.180 ms
    2010-05-28 01:00:17 [sql_helper] DEBUG: Created partitioned table for reports.session_counts ('2010-05-27' -> '2010-05-28')
    2010-05-28 01:00:18 [sql_helper] DEBUG: __make_session_counts_table (reports/node/untangle_vm:316) took 1188.638 ms
    2010-05-28 01:00:18 [engine] DEBUG: registering fact table: 'reports.session_totals': '<reports.engine.FactTable instance at 0x96c88cc>'
    2010-05-28 01:00:18 [sql_helper] DEBUG: __get_branded_name (reports/node/untangle_vm:86) took 1.019 ms
    2010-05-28 01:00:18 [sql_helper] DEBUG: setup (reports/node/untangle_vm:60) took 4333.730 ms
    2010-05-28 01:00:18 [engine] DEBUG: doing setup for: untangle-casing-http (2010-05-27 00:00:00.00 -> 2010-05-28 00:00:00.00)
    2010-05-28 01:00:18 [sql_helper] WARNING: could not access database, getting new connection
    Traceback (most recent call last):
    File "/usr/lib/python2.5/reports/sql_helper.py", line 75, in get_connection
    curs.execute("SELECT 1")
    ProgrammingError: ERROR: current transaction is aborted, commands ignored until end of transaction block

    SELECT 1
    2010-05-28 01:00:18 [engine] WARNING: could not setup for: untangle-casing-http
    Traceback (most recent call last):
    File "/usr/lib/python2.5/reports/engine.py", line 415, in setup
    node.setup(start_date, end_date)
    File "/usr/lib/python2.5/reports/sql_helper.py", line 45, in wrapper
    res = func(*arg)
    File "/usr/lib/python2.5/reports/node/untangle_casing_http.py", line 36, in setup
    self.__create_n_http_events(start_date, end_date)
    File "/usr/lib/python2.5/reports/sql_helper.py", line 45, in wrapper
    res = func(*arg)
    File "/usr/lib/python2.5/reports/node/untangle_casing_http.py", line 72, in __create_n_http_events
    'time_stamp', start_date, end_date)
    File "/usr/lib/python2.5/reports/sql_helper.py", line 173, in create_partitioned_table
    (DateFromMx(d), DateFromMx(d + mx.DateTime.DateTimeDelta(1))))
    File "/usr/lib/python2.5/reports/sql_helper.py", line 128, in run_sql
    connection.rollback()
    InterfaceError: already closed
    2010-05-28 01:00:18 [engine] DEBUG: doing setup for: untangle-node-webfilter (2010-05-27 00:00:00.00 -> 2010-05-28 00:00:00.00)
    2010-05-28 01:00:18 [sql_helper] DEBUG: __update_n_http_events (reports/node/untangle_base_webfilter:122) took 281.511 ms
    2010-05-28 01:00:18 [engine] WARNING: could not setup for: untangle-node-webfilter
    Traceback (most recent call last):
    File "/usr/lib/python2.5/reports/engine.py", line 415, in setup
    node.setup(start_date, end_date)
    File "/usr/lib/python2.5/reports/sql_helper.py", line 45, in wrapper
    res = func(*arg)
    File "/usr/lib/python2.5/reports/node/untangle_base_webfilter.py", line 70, in setup
    ft.measures.append(Column('wf_%s_blocks' % self.__vendor_name,
    AttributeError: 'NoneType' object has no attribute 'measures'
    2010-05-28 01:00:18 [engine] DEBUG: doing setup for: untangle-node-spyware (2010-05-27 00:00:00.00 -> 2010-05-28 00:00:00.00)
    2010-05-28 01:00:19 [sql_helper] DEBUG: __update_access (reports/node/untangle_node_spyware:114) took 142.987 ms
    2010-05-28 01:00:19 [engine] WARNING: could not setup for: untangle-node-spyware
    Traceback (most recent call last):
    File "/usr/lib/python2.5/reports/engine.py", line 415, in setup
    node.setup(start_date, end_date)
    File "/usr/lib/python2.5/reports/node/untangle_node_spyware.py", line 55, in setup
    self.__update_blacklist(start_date, end_date)
    File "/usr/lib/python2.5/reports/sql_helper.py", line 45, in wrapper
    res = func(*arg)
    File "/usr/lib/python2.5/reports/node/untangle_node_spyware.py", line 180, in __update_blacklist
    ft.measures.append(Column('sw_blacklisted', 'integer',
    AttributeError: 'NoneType' object has no attribute 'measures'
    2010-05-28 01:00:19 [engine] DEBUG: doing setup for: untangle-casing-mail (2010-05-27 00:00:00.00 -> 2010-05-28 00:00:00.00)
    2010-05-28 01:00:19 [engine] WARNING: could not setup for: untangle-casing-mail
    Traceback (most recent call last):
    File "/usr/lib/python2.5/reports/engine.py", line 415, in setup
    node.setup(start_date, end_date)
    File "/usr/lib/python2.5/reports/sql_helper.py", line 45, in wrapper
    res = func(*arg)
    File "/usr/lib/python2.5/reports/node/untangle_casing_mail.py", line 36, in setup
    self.__create_n_mail_msgs(start_date, end_date)
    File "/usr/lib/python2.5/reports/sql_helper.py", line 45, in wrapper
    res = func(*arg)
    File "/usr/lib/python2.5/reports/node/untangle_casing_mail.py", line 217, in __create_n_mail_msgs
    'time_stamp', start_date, end_date)
    File "/usr/lib/python2.5/reports/sql_helper.py", line 173, in create_partitioned_table
    (DateFromMx(d), DateFromMx(d + mx.DateTime.DateTimeDelta(1))))
    File "/usr/lib/python2.5/reports/sql_helper.py", line 128, in run_sql
    connection.rollback()
    InterfaceError: already closed
    2010-05-28 01:00:19 [engine] DEBUG: doing setup for: untangle-node-clam (2010-05-27 00:00:00.00 -> 2010-05-28 00:00:00.00)
    2010-05-28 01:00:19 [sql_helper] DEBUG: __update_n_http_events (reports/node/untangle_base_virus:152) took 23.545 ms
    2010-05-28 01:00:19 [sql_helper] DEBUG: __update_n_mail_table (reports/node/untangle_base_virus:187) took 170.882 ms
    2010-05-28 01:00:19 [sql_helper] DEBUG: __update_n_mail_table (reports/node/untangle_base_virus:187) took 227.150 ms
    2010-05-28 01:00:19 [engine] WARNING: could not setup for: untangle-node-clam
    Traceback (most recent call last):
    File "/usr/lib/python2.5/reports/engine.py", line 415, in setup
    node.setup(start_date, end_date)
    File "/usr/lib/python2.5/reports/sql_helper.py", line 45, in wrapper
    res = func(*arg)
    File "/usr/lib/python2.5/reports/node/untangle_base_virus.py", line 71, in setup
    ft.measures.append(Column('viruses_%s_blocked' % self.__vendor_name,
    AttributeError: 'NoneType' object has no attribute 'measures'
    2010-05-28 01:00:19 [engine] DEBUG: doing setup for: untangle-node-reporting (2010-05-27 00:00:00.00 -> 2010-05-28 00:00:00.00)
    2010-05-28 01:00:19 [engine] WARNING: could not setup for: untangle-node-reporting
    Traceback (most recent call last):
    File "/usr/lib/python2.5/reports/engine.py", line 415, in setup
    node.setup(start_date, end_date)
    File "/usr/lib/python2.5/reports/sql_helper.py", line 45, in wrapper
    res = func(*arg)
    File "/usr/lib/python2.5/reports/node/untangle_server.py", line 56, in setup
    self.__create_n_server_events(start_date, end_date)
    File "/usr/lib/python2.5/reports/sql_helper.py", line 45, in wrapper
    res = func(*arg)
    File "/usr/lib/python2.5/reports/node/untangle_server.py", line 133, in __create_n_server_events
    swap_free INT8)""", 'time_stamp', start_date, end_date)
    File "/usr/lib/python2.5/reports/sql_helper.py", line 173, in create_partitioned_table
    (DateFromMx(d), DateFromMx(d + mx.DateTime.DateTimeDelta(1))))
    File "/usr/lib/python2.5/reports/sql_helper.py", line 128, in run_sql
    connection.rollback()
    InterfaceError: already closed
    I also have removed & re-added he report module as well as rebooted several times.

  9. #19
    Master Untangler k6rtm's Avatar
    Join Date
    Feb 2010
    Location
    Silicon Valley
    Posts
    110

    Default

    I haven't seen reports since the 7.3 upgrade; I rebooted the system about 18 hours after doing the upgrade. No e-mails on report availability, and logging into the client directly, reports are not available. Will do terminal commands tonight when I'm in front of the box.

    bob in sunny silicon valley

  10. #20
    Untangle Ninja mrunkel's Avatar
    Join Date
    Jul 2008
    Posts
    3,022

    Default

    bug filed: 7825
    m.
    <BR>
    Big Frickin Disclaimer:
    While I'm pretty sure, I can't guarantee that I know what I'm doing. There might be a better way to do this, and this way might actually suck. Make sure you understand the implications of what you're doing before trying to follow these directions.
    <BR>It often helps troubleshooting if you have a good network map. Look <A HREF="http://forums.untangle.com/tip-day/5407-how-draw-network-diagram.html">here</A> if you want my advice on how to draw one. <BR> <B>Attention: Support and help on the Untangle Forums is provided by volunteers and community members like yourself.
    If you need Untangle support please call or email support@untangle.com<B>

Page 2 of 4 FirstFirst 1234 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

SEO by vBSEO 3.6.0 PL2