Very strange database problems...

[Mas*Mind]

Since I moved my forum to a new server (this version is still running 1.1.3 (will upgrade soon) the errorlog of mysql is flooded with error messages...

the strangest thing is that it seems to occur exact every 1 minute:

Apr 10 13:05:37 feyenoord login[5813]: FAILED LOGIN 3 FROM (null) FOR Disconnected, Authentication failure
Apr 10 13:06:38 feyenoord PAM_unix[5933]: check pass; user unknown
Apr 10 13:06:38 feyenoord PAM_unix[5933]: authentication failure; LOGIN(uid=0) -> Enter Password: * for system-auth service
Apr 10 13:06:38 feyenoord login[5933]: FAILED LOGIN 1 FROM (null) FOR Enter Password: *, Authentication failure
Apr 10 13:07:38 feyenoord PAM_unix[6044]: check pass; user unknown
Apr 10 13:07:38 feyenoord PAM_unix[6044]: authentication failure; LOGIN(uid=0) -> Enter Password: * for system-auth service
Apr 10 13:07:38 feyenoord login[6044]: FAILED LOGIN 1 FROM (null) FOR Enter Password: *, Authentication failure
Apr 10 13:07:38 feyenoord PAM_unix[6044]: check pass; user unknown
Apr 10 13:07:38 feyenoord PAM_unix[6044]: authentication failure; LOGIN(uid=0) -> nter Password: for system-auth service
Apr 10 13:07:38 feyenoord login[6044]: FAILED LOGIN 2 FROM (null) FOR nter Password: , Authentication failure

I've absolutely no clue where it comes from, but it happens since I transfered the server so I guess it has to do something with vb. But I doubt it because I never had any of these problems and never heard of something like this...

It's a serieus problem, because the logfile is growing huge and caused mysql to crash a couple of times...

[John]

Mas*Mind

The first thing that springs to mind is CRON - do you have any automated CRON scripts that try to access the database?

Try recreating those error log lines by hand, by logging in with incorrect passwords into MySQL, and see what happens. See if you can figure out exactly what it is that creates them.

Do you have any other PHP scripts on the server that access the database?

John

[Mas*Mind]

That's the first thing I thought about too....but I really have no cron-job running so this is totally confusing me

I have another script running yes, but that ran allready weeks like it should...This happened just when I transfered my forum...And I checked all scripts that may cause this, with no result...

[Mas*Mind]

It came out the mysqlcrashes weren't caused by my above described problem (that one still bumps my head btw) but that vbulletin (1.1.3) creates an enormous amount of mysql-instances...sometimes there were 60+ open mysql-instances...

I know 1.1.3 is an old version and I'll upgrade as soon as I have my 2.0 version ready (upgrading to 1.1.6 is not an option, I've hacked my version quite)

But is this a known issue with 1.1.3 and can this be confirmed???

And is this something that surely is solved with the 2.0 version?

The strangest thing is I never heard something of it from my old host (site5), but they did threw (not really, they politely asked us to move) us from their server because we were too resource-intensitive....