A not so neat one. Not liking this log file

Openfire Openfire Dev
1

Ok, looking at the logs, please pay attention to found old database entries… I have modified the wildfire_postgres.sql script in the root database dir to allow for usernames up to 64 chars, but it still should only change this once.

https://myserver.mydomain:9091

2006.05.24 15:01:00 Initializing Asterisk-IM Plugin

2006.05.24 15:14:15 unloading asterisk-im plugin resources

2006.05.24 15:14:15 Unregistering asterisk-im plugin as a component

2006.05.24 15:14:52 Found old database version 8 for wildfire. Upgrading to version 9…

2006.05.24 15:14:52 Database update successful.

2006.05.24 15:14:53 Publish-Subscribe domain: pubsub.myserver.mydomain.com

2006.05.24 15:14:53 Started server (unencrypted) socket on port: 5269

2006.05.24 15:14:53 Started multiplexer (unencrypted) socket on port: 5262

2006.05.24 15:14:53 Started component (unencrypted) socket on port: 15347

2006.05.24 15:14:53 Started plain (unencrypted) socket on port: 5222

2006.05.24 15:14:53 Started SSL (encrypted) socket on port: 5223

2006.05.24 15:14:53 Multi User Chat domain: conference.myserver.mydomain.com

2006.05.24 15:14:53 Wildfire 3.0.0 Alpha

2006.05.24 15:14:56 Admin console listening at:

http://myserver.mydomain.com:9090

https://myserver.mydomain.com:9091

2006.05.24 15:14:56 Initializing Asterisk-IM Plugin

2006.05.25 07:07:44 unloading asterisk-im plugin resources

2006.05.25 07:07:44 Unregistering asterisk-im plugin as a component

2006.05.25 07:08:58 Found old database version 8 for wildfire. Upgrading to version 9…

2006.05.25 07:08:58 Database update successful.

2006.05.25 07:08:59 Publish-Subscribe domain: pubsub.myserver.mydomain.com

2006.05.25 07:08:59 Started server (unencrypted) socket on port: 5269

2006.05.25 07:08:59 Started multiplexer (unencrypted) socket on port: 5262

2006.05.25 07:08:59 Started component (unencrypted) socket on port: 15347

2006.05.25 07:08:59 Started plain (unencrypted) socket on port: 5222

2006.05.25 07:08:59 Started SSL (encrypted) socket on port: 5223

2006.05.25 07:08:59 Multi User Chat domain: conference.myserver.mydomain.com

2006.05.25 07:08:59 Wildfire 3.0.0 Alpha

2006.05.25 07:09:02 Admin console listening at:

http://im2.sanmina-sci.com:9090

https://im2.sanmina-sci.com:9091

2006.05.25 07:09:02 Initializing Asterisk-IM Plugin

2006.05.25 07:09:47 unloading asterisk-im plugin resources

2006.05.25 07:09:47 Unregistering asterisk-im plugin as a component

2006.05.25 07:17:08 Found old database version 8 for wildfire. Upgrading to version 9…

2006.05.25 07:17:08 Database update successful.

2006.05.25 07:17:08 Publish-Subscribe domain: pubsub.myserver.mydomain.com

2006.05.25 07:17:08 Started server (unencrypted) socket on port: 5269

2006.05.25 07:17:08 Started multiplexer (unencrypted) socket on port: 5262

2006.05.25 07:17:08 Started component (unencrypted) socket on port: 15347

2006.05.25 07:17:08 Started plain (unencrypted) socket on port: 5222

2006.05.25 07:17:09 Started SSL (encrypted) socket on port: 5223

2006.05.25 07:17:09 Multi User Chat domain: conference.myserver.mydomain.com

2006.05.25 07:17:09 Wildfire 3.0.0 Alpha

2006.05.25 07:17:11 Admin console listening at:

http://myserver.mydomain.com:9090

https://myserver.mydomain.com:9091

2006.05.25 07:17:11 Initializing Asterisk-IM Plugin

Any suggestions?

Jeff

2

Hi Jeff,

does the script contain a line

UPDATE jiveVersion set version=9 where name = ‘‘wildfire’’;

? I always wonder why no “commit;” is in the script, maybe you need to add it.

LG

3

yes, it has dir /9 and the script only includes the command

UPDATE jiveVersion set version=9 where name = ‘‘wildfire’’;

without COMMIT,

However AFAIK the scripts have never included a COMMIT entry, since there is no BEGIN WORK entry to open.

UPDATE: running the command from just the psql prompt it will update the table, using BEGIN WORK it will update the table. So why doesn;t it work in the script… hmmm…

Jeff

Message was edited by: jeff_garner

4

Hi Jeff,

the scripts did indeed never contain a commit and I did always wonder why Jivesoftware delivers these scripts without commit. It does no harm and if one wants to update the database manually one must always commit the script.

Maybe one did change the update process without adjusting the scripts?

LG