Issues after moving from 2.0n Beta to 2.0

[manu]

Like it

Up

0

Down

Drop it

::

1.3 to 2.0 or 1.3.1 to 2.0?

[godzone]

Like it

Up

0

Down

Drop it

::

To be honest I am not sure, I started off with the 1.3 VMImage, then upgraded to 2.0n beta and ran the conversion tool. Then have upgraded to 2.0 final but didn’t do any conversion. I have run the SQL to update the values of id_modulo from 0 to 2.

[godzone]

Like it

Up

0

Down

Drop it

::

And unfortunately I delete the 1.3 stuff when I upgrade to 2.0 beta ( not 2.0n typo) so I don’t recall if it was 1.3 or 1.3.1

[godzone]

Like it

Up

0

Down

Drop it

::

I have checked the ‘tservers’ table and the status for all is ‘1’ yet in the web interface, they display with RED status and are being considered down 🙁

[manu]

Like it

Up

0

Down

Drop it

::

Alright, stop all the servers, make sure they don’t even appear in: ps aux | grep -i pandora if the do, kill them

Now, do this:

/usr/local/bin/pandora_server /etc/pandora/pandora_server.conf

Any error?

[godzone]

Like it

Up

0

Down

Drop it

::

Ok, I have just done that and there are no errors.

I put a print_r after the get_db_all_rows( tserver ) in godmode/servers/modificar_server, to see what the web ui thought was in the database. It shows

[0] => 4 [id_server] => 4 [1] => agree-22_Data [name] => agree-22_Data [2] => [ip_address] => [3] => 0 [status] => 0 [4] => 2008-11-08 03:04:44 [laststart] => 2008-11-08 03:04:44 [5] => 2008-11-08 03:04:54 [keepalive] => 2008-11-08 03:04:54 [6] => 0 [snmp_server] => 0 [7] => 0 [network_server] => 0 [8] => 1 [data_server] => 1 [9] => 1 [master] => 1 [10] => 0 [checksum] => 0 [11] => Autocreated at startup [description] => Autocreated at startup [12] => 0 [recon_server] => 0 [13] => 2.0 (P) PS081029 [version] => 2.0 (P) PS081029 [14] => 0 [plugin_server] => 0 [15] => 0 [prediction_server] => 0 [16] => 0 [wmi_server] => 0 [17] => 0 [export_server] => 0 ) Array ( [0] => 5 [id_server] => 5

If I use phpmyAdmin to look at the same database and same table I get,
Edit Delete 4 agree-22_Data 1 2008-11-08 03:04:57 2008-11-08 03:08:28 0 0 1 1 0 Autocreated at startup 0 2.0 (P) PS081029 0 0 0 0

I am no mysql expert but I don’t understand how pandora_console does a slect and get status=0 and phpmyadmin does a select and gets a status=1

[godzone]

Like it

Up

0

Down

Drop it

::

OK, I have finally tracked down the issue. With a bunch of test not working. Simply speaking, the config parsing code for all the timeouts is broken. It only allows a single digit. e.g.

elsif ($parametro =~ m/^tcp_timeouts([0-9])/i) {
$pa_config->{“tcp_timeout”} = clean_blank($1);
}

The RE needs to be ([0-9]+) or better (d+)

I had changed the timeout from the default 30 to 15, which actually resulted in it being just 1!! which isn’t long enough. I’ll post to the developers list as well.

[manu]

Like it

Up

0

Down

Drop it

::

We’re going to take a look at it and fix it in the svn

[godzone]

Like it

Up

0

Down

Drop it

::

Great, I am now going to try to get to the bottom of the server all showing as down, when they are not.

[godzone]

Like it

Up

0

Down

Drop it

::

OK, I don’t understand what was wrong but changing the timezone and locale to NZ and en-US.UTF-8 respectively the rebooting seems to have resolved the server issue.