Hello,
Not sure how serious of an issue this is...
But going over our logs, due to another issue, we
find alot of occurances where the username is appearing as ((null)):
[20081222 12:12:44] [xx.xx.x.xx] connecting
[20081222 12:12:44] [xx.xx.x.xx] connected
[20081222 12:12:44] [xx.xx.x.xx] disconnected ((null))
We have a similar issue that occurs as the day goes on...
Our main server has many connections each hour, with many users connecting with several sessions each 5 minutes. This server will eventually no longer take logins, reporting the ((null)) username in the logs. To get around this issue, we restart the FTP service every 24 hours (automatically).
Our test server, receives few connections, and does not run into this issue.
Any thoughts, suggestions ?
Regards,
Don Hunter
((null)) username appearing in logs
Not bots...
Hello,
Thanks for the reply.
We wil install the latest version.
This is not caused by bots, as the IP is the same as others that have valid users (and in many cases our own internal IP).
Don
Thanks for the reply.
We wil install the latest version.
This is not caused by bots, as the IP is the same as others that have valid users (and in many cases our own internal IP).
Don
Hi,
Did installing the new version solve your problem?
Because we had the same problem here...
If we check our logs, seems to be occuring everytime when 2 concurent logons were happening:
[20090305 09:42:52] [ipadres] connecting
[20090305 09:42:52] [ipadres] connected
[20090305 09:42:53] [ipadres] prdadm, download of '/200902/802000408850.pdf'
[20090305 09:42:53] [ipadres] disconnected (prdadm)
[20090305 09:46:33] [ipadres] connecting
[20090305 09:46:33] [ipadres] connected
[20090305 09:46:34] [ipadres] prdadm, download of '/200902/801000115851.pdf'
[20090305 09:46:34] [ipadres] disconnected (prdadm)
[20090305 09:47:55] [ipadres] connecting
[20090305 09:47:55] [ipadres] connected
[20090305 09:47:55] [ipadres] connecting
[20090305 09:47:55] [ipadres] connected
[20090305 09:47:56] [ipadres] prdadm, download of '/200902/802000441586.pdf'
[20090305 09:47:56] [ipadres] prdadm, download of '/200901/801000115851.pdf'
[20090305 09:47:56] [ipadres] disconnected (prdadm)
[20090305 09:47:56] [ipadres] disconnected (prdadm)
[20090305 09:48:51] [ipadres] connecting
[20090305 09:48:51] [ipadres] connected
[20090305 09:48:52] [ipadres] disconnected ((null))
In our case, the ipadres is always the same.
Regards,
Günther
Ps. Build 250
Did installing the new version solve your problem?
Because we had the same problem here...
If we check our logs, seems to be occuring everytime when 2 concurent logons were happening:
[20090305 09:42:52] [ipadres] connecting
[20090305 09:42:52] [ipadres] connected
[20090305 09:42:53] [ipadres] prdadm, download of '/200902/802000408850.pdf'
[20090305 09:42:53] [ipadres] disconnected (prdadm)
[20090305 09:46:33] [ipadres] connecting
[20090305 09:46:33] [ipadres] connected
[20090305 09:46:34] [ipadres] prdadm, download of '/200902/801000115851.pdf'
[20090305 09:46:34] [ipadres] disconnected (prdadm)
[20090305 09:47:55] [ipadres] connecting
[20090305 09:47:55] [ipadres] connected
[20090305 09:47:55] [ipadres] connecting
[20090305 09:47:55] [ipadres] connected
[20090305 09:47:56] [ipadres] prdadm, download of '/200902/802000441586.pdf'
[20090305 09:47:56] [ipadres] prdadm, download of '/200901/801000115851.pdf'
[20090305 09:47:56] [ipadres] disconnected (prdadm)
[20090305 09:47:56] [ipadres] disconnected (prdadm)
[20090305 09:48:51] [ipadres] connecting
[20090305 09:48:51] [ipadres] connected
[20090305 09:48:52] [ipadres] disconnected ((null))
In our case, the ipadres is always the same.
Regards,
Günther
Ps. Build 250
Last edited by gadvogel on Thu Mar 05, 2009 10:19 am, edited 1 time in total.
ongoing occurance
Good morning,
Our issue has been ongoing since initial install.
Un-install, then re-install, plus upgrade has not resolved the issue.
We also have to restart the service every 24 hours, or the application stops responding.
Regards,
Don
Our issue has been ongoing since initial install.
Un-install, then re-install, plus upgrade has not resolved the issue.
We also have to restart the service every 24 hours, or the application stops responding.
Regards,
Don