Not logging any SYN requests on port 9090, so there’‘s something else going on. I modified the config file’'s insecure port setting to any one of the (slightly offbeat) ports (like, not 80) that are open and available with the same results.
What about the ‘‘jive’’ user? Is it supposed to be able to login?
I saw another post in these forums that described /var/log/messages’’ output as something like:
Dec 11 12:45:43 mail su(pam_unix)[27463]: session opened for user jive by (uid=0)
Dec 11 12:45:44 mail su(pam_unix)[27463]: wildfire startup stuff
Dec 11 12:45:45 mail su(pam_unix)[27463]: more wildfire stuff
Dec 11 12:45:48 mail su(pam_unix)[27463]: session closed for user jive
I’'ve never been able to get anything other than the ~1 second transaction:
Dec 11 12:45:43 mail su(pam_unix)[27463]: session opened for user jive by (uid=0)
Dec 11 12:45:43 mail su(pam_unix)[27463]: session closed for user jive
The jive user and group are established, however jive user is set to temporarily disable login. If I remove that flag, jive gets set to no password required. I can’‘t locate anything that would allow me to establish/change jive’'s password so it actually uses one without getting set to temporarily disable login. Is this normal?
Wildfired is definitely starting and using resources and the ports it uses are free and clear, so I’‘ve got to imagine, given the evidence, that it’'s a jive user issue of some kind.
Here’'s the tail of my info.log file. Note the timestamp in relation to the /var/log/messages timestamp above for the same startup attempt:
2006.12.11 12:45:48 Multi User Chat domain: conference.mydomain.com
2006.12.11 12:45:48 Publish-Subscribe domain: pubsub.mydomain.com
2006.12.11 12:45:48 Started server (unencrypted) socket on port: 5269
2006.12.11 12:45:48 Started plain (unencrypted) socket on port: 5222
2006.12.11 12:45:51 Started SSL (encrypted) socket on port: 5223
2006.12.11 12:45:52 Wildfire 3.1.1 [Dec 11, 2006 12:45:52 PM]
2006.12.11 12:46:03 Admin console listening at:
http://mydomain.com:9090
https://mydomain.com:9091
Looks pretty normal. No errors in the other wildfire logs … Normal?
Thanks again, it2000.