Exception when changing to process_checks about amon

[martinrusev]

Hi @mjs7231

Did you restart amond and amon after changing the string - I am working to remove the restart step, but for now - it has to be restarted after any configuration change.
Also - is the problem persistent or it occurs only in the first minute?

[pkkid]

The problem is persistent. I had the server running all night and there is still a stacktrace on the Dashboard page. All other pages appear to work fine. I have been restarting the server on configuration changes. This morning I tried a full stop / start sequence, but the problem is still here.

If I switch process_checks back to only contain "mongo" the problem goes away. Problem is that is not a process I care to monitor. :)

[martinrusev]

Can you please share your OS environment and if its 64/32 bit

[pkkid]

I'm running on Ubuntu 11.04 x64 in Virtualbox on a Win7 host. - Linux vbox-natty 2.6.38-13-generic #53-Ubuntu SMP Mon Nov 28 19:33:45 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux.

[martinrusev]

Can you please check if the config file is a valid json http://jsonlint.com/
Because if its not Amon tries to provide some reasonable defaults, but the processes are 100% user defined, so it can't do anything about that and just fails :)

[pkkid]

I ran it through jslint, and it's valid.

{
    "acl": "False",
    "system_check_period": 60,
    "secret_key": "KQIIHloaREKypDq/cFmRQKAJDwxlokV7v+vPaGhzSAg=",
    "process_checks": [
        "apache"
    ],
    "web_app": {
        "host": "127.0.0.1",
        "port": "2464"
    },
    "backend": {
        "mongo": {
            "host": "127.0.0.1",
            "port": 27017
        }
    }
}

I added the following line just before the exception line:

open('/tmp/foobar.txt', 'w+').write("'%s' (%s)\n" % (variable, type(variable)))

The output of that line is:

'' (<class 'jinja2.runtime.Undefined'>)

[pkkid]

You know what. Apache is not running on my dev system. So I thought thta might be it. I switched the process from "apache" to "postgres" in the config posted above. Problem is still there, same output as before as well.

Running "ps aux | grep postgres" on my system yeilds the following output:

postgres   897  0.0  0.1 105452  6724 ?        S    Jan06   0:02 /usr/lib/postgresql/8.4/bin/postgres -D /var/lib/postgresql/8.4/main -c
config_file=/etc/postgresql/8.4/main/postgresql.conf
postgres  1001  0.0  0.0 105452  1668 ?        Ss   Jan06   0:44 postgres: writer process                                                                                                    
postgres  1002  0.0  0.0 105452  1428 ?        Ss   Jan06   0:37 postgres: wal writer process                                                                                                
postgres  1003  0.0  0.0 105760  1968 ?        Ss   Jan06   0:11 postgres: autovacuum launcher process                                                                                       
postgres  1004  0.0  0.0  77140  1636 ?        Ss   Jan06   0:06 postgres: stats collector process                                                                                           
mjs7231  17127  0.0  0.0  13128  1056 pts/1    S+   13:22   0:00 grep --color postgres

[martinrusev]

Weird, I am running tests and I will update you in the moment I have a solution. Sorry for the troubles

[pkkid]

No need to apologize, this is an awesome little webapp. I look forward to deploying it on my site. :)

[micsco]

mjs7231 - we had the same issue when just configuring ours. Make sure you restart amond as well as amon. Just restarting amon causes this error, restarting both and you're away laughing.

[pkkid]

Ahh! -- That does indeed fix it for me a well, thanks alot! :)

EDIT: MUAHAHA!!

[mutewinter]

Restarting amond also fixed this issue for me.

sudo /etc/init.d/amond restart