Page 1 of 4 123 ... LastLast
Results 1 to 10 of 31
  1. #1
    Newbie
    Join Date
    May 2010
    Posts
    11

    Default Reporting Still Not Working - DB problem?

    Hey y'all. Would this be a good place to ask a question/report an issue with the Beta? I have installed the 7.3 beta on the recommendation of the support tech since we couldn't get 7.2 to install properly on our Dell 2850. 7.3B went on flawlessly, the only issue that we are having is that we are not getting ANY reports. This has been up and running since last Friday, so I have passed the 24hr time frame. I was curious if anyone else experienced this. Is there a log somewhere where I could look to see possibly why the reports are not getting generated? The only thing I get is something like "Check back in the morning for your reports" when I click on the View Repors button. Any help would be greatly appreciated.

    Thank you!

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

    Default

    hi Symo,

    welcome to the forums.

    you can check /var/log/uvm/reporter.log
    just run 'less /var/log/uvm/reporter.log'

    there will probably be an error or something in there. if you aren't sure what it means just paste it here.
    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. #3
    Newbie
    Join Date
    May 2010
    Posts
    11

    Default

    Quote Originally Posted by dmorris View Post
    hi Symo,

    welcome to the forums.

    you can check /var/log/uvm/reporter.log
    just run 'less /var/log/uvm/reporter.log'

    there will probably be an error or something in there. if you aren't sure what it means just paste it here.
    Thanks for the response... In looking through this error log, I'm seeing several errors... I will past a few below...

    Code:
    2010-05-17 01:53:11 [engine] DEBUG: doing setup for: untangle-casing-http (2010-05-16 00:00:00.00 -> 2010-05-17 00:00:00.00)
    2010-05-17 01:53:11 [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-17 01:53:11 [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
    Code:
    2010-05-17 01:53:11 [engine] DEBUG: doing setup for: untangle-node-webfilter (2010-05-16 00:00:00.00 -> 2010-05-17 00:00:00.00)
    2010-05-17 01:53:11 [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
    Code:
    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-16'
      AND reports.n_http_events.time_stamp < '2010-05-17'
      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-17 01:53:11 [engine] DEBUG: doing setup for: untangle-node-adconnector (2010-05-16 00:00:00.00 -> 2010-05-17 00:00:00.00)
    2010-05-17 01:53:11 [engine] WARNING: could not setup for: untangle-node-adconnector
    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_adconnector.py", line 46, in setup
        self.__create_n_adlogin_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_node_adconnector.py", line 105, in __create_n_adlogin_events
        client_addr inet)""",  '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-17 01:53:11 [engine] DEBUG: doing setup for: untangle-node-spyware (2010-05-16 00:00:00.00 -> 2010-05-17 00:00:00.00)
    2010-05-17 01:53:11 [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 54, in setup
        self.__update_access(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 142, in __update_access
        raise e
    ProgrammingError: ERROR:  column "sw_access_ident" of relation "sessions" does not exist
    LINE 2: SET sw_access_ident = ident
                ^
    What do y'all think? Is it looking like a problem in accessing the database?

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

    Default

    Yes, your database is inaccessible. What does "psql -U postgres uvm" output?
    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>

  5. #5
    Newbie
    Join Date
    May 2010
    Posts
    11

    Default

    Quote Originally Posted by mrunkel View Post
    Yes, your database is inaccessible. What does "psql -U postgres uvm" output?
    Code:
    / # psql -U postgres uvm                                                                                                                                                [root @ untangle]
    Welcome to psql 8.3.9, the PostgreSQL interactive terminal.
    
    Type:  \copyright for distribution terms
           \h for help with SQL commands
           \? for help with psql commands
           \g or terminate with semicolon to execute query
           \q to quit
    
    uvm=#
    Thank you taking the time to help.

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

    Default

    can you check /var/log/uvm/monit.log?

    does it say anything about the database?

    what are the specs on this box?
    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

  7. #7
    Newbie
    Join Date
    May 2010
    Posts
    11

    Default

    Quote Originally Posted by dmorris View Post
    can you check /var/log/uvm/monit.log?

    does it say anything about the database?

    what are the specs on this box?
    Really only thing in monit.log regarding postgres are the following lines:
    Code:
    [CDT May 19 01:21:01] debug    : 'postgres' zombie check succeeded [status_flag=0000]
    [CDT May 19 01:21:01] debug    : monitor service 'postgres' on user request
    [CDT May 19 01:21:01] info     : monit daemon at 8988 awakened
    [CDT May 19 01:21:01] debug    : 'postgres' succeeded connecting to UNIX[/var/run/postgresql/.s.PGSQL.5432]
    [CDT May 19 01:21:01] debug    : 'postgres' succeeded testing protocol [PGSQL] at UNIX[/var/run/postgresql/.s.PGSQL.5432]
    I did see these lines as well:
    Code:
    [CDT May 19 01:20:34] debug    : 'spamlog2' Regular expression 'bayes: cannot open bayes databases /home/spamc/.spamassassin/bayes_\* R/W: lock failed: Interrupted system call' doesn't match on content line
    [CDT May 19 01:20:34] debug    : 'spamlog2' Regular expression 'bayes: cannot open bayes databases /home/spamc/.spamassassin/bayes_\* R/W: lock failed: Interrupted system call' doesn't match on content line
    Which is slightly interesting because the Spam filter isn't even supposed to be running... I've now since removed it.

    The machine is a Dell PowerEdge 2850 (2U Rackmount) with 4Gig Ram and dual Xeon 2.8Ghz processors (Shows up as 8 cores.)

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

    Default

    go and look for upgrades and then upgrade.

    then reboot the machine to get a clean state (or reboot postgres with /etc/init.d/postgresql restart)
    then wait until tomorrow and see if it works.
    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

  9. #9
    Newbie
    Join Date
    May 2010
    Posts
    11

    Default

    Quote Originally Posted by dmorris View Post
    go and look for upgrades and then upgrade.

    then reboot the machine to get a clean state (or reboot postgres with /etc/init.d/postgresql restart)
    then wait until tomorrow and see if it works.
    Well there definitely were upgrades to be applied! So I did that. I went ahead and restarted postgresql, haven't rebooted yet... Don't want to get screamed at. I'll reboot as soon as I can safely.

    I have looked at the database, and there seems to be PLENTY of data in there!!! Would I really have to wait for the cron job to kickoff, or should I be able to run the reporting script manually to at least process yesterday's data?

  10. #10
    Newbie
    Join Date
    May 2010
    Posts
    11

    Default

    Good Morning All....

    Well after letting it run and try to see if the cron job works... still no go. No reports... same errors.

Page 1 of 4 123 ... 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