Am 10.09.2011 19:21, schrieb a.sm...@ukgrid.net:
> Hi Walter/all,
>
> ok nailed it, the issue is the default hosts.allow installed on FreeBSD,
> and specifically the last section that
> denies everything. By default it looks like this:
>
> # The rest of the daemons are protected.
> ALL : ALL
Hi Walter/all,
ok nailed it, the issue is the default hosts.allow installed on
FreeBSD, and specifically the last section that denies everything. By
default it looks like this:
# The rest of the daemons are protected.
ALL : ALL \
: severity auth.info \
: twist /bin/echo "Y
Am 10.09.2011 19:02, schrieb a.sm...@ukgrid.net:
> Quoting Reindl Harald :
>
>>
>> "You are not welcome to use mysqld from tau" is NOT from mysqld
>> remove your hosts.allow/hosts.deny crap and replace it with firewall-rules
>> if the problem goes away make a bugreport on BSD side becahuse this
Quoting Reindl Harald :
"You are not welcome to use mysqld from tau" is NOT from mysqld
remove your hosts.allow/hosts.deny crap and replace it with firewall-rules
if the problem goes away make a bugreport on BSD side becahuse this
is NOT a mysqld issue
I've already established that the is
Am 10.09.2011 18:52, schrieb a.sm...@ukgrid.net:
> Quoting walter harms :
>
>> restart it with the same parameter on the command line and see what happens
>> the server support a verbos option (never used) perhaps it will tell you
>> more.
>>
>
> I can start mysqld direct from the command line an
Quoting walter harms :
restart it with the same parameter on the command line and see what happens
the server support a verbos option (never used) perhaps it will tell
you more.
I can start mysqld direct from the command line and reproduce the
problem. I checked and it seems the verbose
Am 10.09.2011 17:32, schrieb a.sm...@ukgrid.net:
> Quoting walter harms :
>
>> I still do not see why it is restarting ... there must be something
>> watching is disappear.
>> Just to be sure, you do from a remote host: mysql -hHOST -ume -e "show
>> tables" ?
>> long shot: Do you have LDAP, NIS
Quoting walter harms :
I still do not see why it is restarting ... there must be something
watching is disappear.
Just to be sure, you do from a remote host: mysql -hHOST -ume -e
"show tables" ?
long shot: Do you have LDAP, NIS or so enabled ?
Ok so made a script as you suggested, and it
Quoting Reindl Harald :
Odd that, so I added a mysql specific line to the hosts.allow
who is using hosts.allow for protection instead a firewall in front
of the machine
or iptables (linux) / ipf (bsd)?
Its used for denyhosts as I mentioned.
As I said I can get it to restart just by doing
Am 10.09.2011 16:25, schrieb a.sm...@ukgrid.net:
> Quoting walter harms :
>
>>
>> What i found odd that your mysqld actualy restarts.
>> Do you have it in some runlevel ? if yes stop and see
>> what happens.
>> If this does not work simple move the mysqld out of he way
>> and replace it with a s
Am 10.09.2011 16:07, schrieb a.sm...@ukgrid.net:
> Then I thought, what if I have hosts.allow misconfigured and its wide open
> maybe a remote system is connecting and
> messing with it. But hosts.allow was correct (mysql not listed, so denied by
> the last all:all). I tested connecting
> from
Quoting walter harms :
What i found odd that your mysqld actualy restarts.
Do you have it in some runlevel ? if yes stop and see
what happens.
If this does not work simple move the mysqld out of he way
and replace it with a script like
#!/bin/sh
echo "mysqld ..." | logger -t TEST
see what ha
Am 10.09.2011 16:07, schrieb a.sm...@ukgrid.net:
> Ok, this is pretty odd but I have found the problem.
>
> Today I have repointed all applications to a different DB server, so I
> have been free to do any testing on the problem server.
>
> I started by dropping the databases one by one, droppe
Ok, this is pretty odd but I have found the problem.
Today I have repointed all applications to a different DB server, so I
have been free to do any testing on the problem server.
I started by dropping the databases one by one, dropped em all and the
issue persisted.
I stopped crond, even t
i bet if he stops crond the problem is going away
anyways i have enough of this thread after "the part for the shutdown"
because if peopole are way too stupid to provide full logs (normally
in the first post) even after requested multiple times they should
learn their lessons the hard way...
This was me restarting MySQL as was requested by Suresh...
Quoting "Singer X.J. Wang" :
This doesn't look like a MySQL issue. Verify that there's no rogue scripts
that shutdowns MySQL...
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http
can you check for any table crashes in the db by using mysqlcheck.
and enable the general log for the database.
On Fri, Sep 9, 2011 at 10:37 PM, wrote:
> No need for that really is there? I posted what was requested.
> The part for the shutdown:
>
> 110909 17:27:31 InnoDB: Starting shutdown...
No need for that really is there? I posted what was requested.
The part for the shutdown:
110909 17:27:31 InnoDB: Starting shutdown...
110909 17:27:32 InnoDB: Shutdown completed; log sequence number 1589339
110909 17:27:32 [Note] /usr/local/libexec/mysqld: Shutdown complete
110909 17:27:32 mys
jesus christ can you post a WHOLE log
this is only a normal start, there is no single line about stop
Am 09.09.2011 18:30, schrieb a.sm...@ukgrid.net:
> Yep, but its basically identical to the info in the logs when its restarting
> itself. I have upgraded to MySQL 5.5
> as of yesterday, so the er
Yep, but its basically identical to the info in the logs when its
restarting itself. I have upgraded to MySQL 5.5 as of yesterday, so
the error info differs due to the version now. Here is the log output:
110909 17:27:35 mysqld_safe Starting mysqld daemon with databases from
/var/db/mysql
can you remove it from service and start it normally using mysqld_safe with
log warnings enabled in the cnf file.
On Fri, Sep 9, 2011 at 4:16 PM, wrote:
> Hi,
>
> that really is the complete error log, that exact same info gets repeated
> over and over, there is zero in the syslog and I get thi
Hi,
that really is the complete error log, that exact same info gets
repeated over and over, there is zero in the syslog and I get this
behaviour when running with no my.cnf (I do obviously have one but I
tried without and it I still see the prob, so that probably makes
things easier fr
Can yo paste the complete error log, Ram memory size and configuration file
here and make sure the machine has enough memory to run the services.
Check the sys log for what is happening just before the service restart.
On Wed, Sep 7, 2011 at 10:51 PM, wrote:
> Hi,
>
> as of yesterday the MySQL
Hi,
as of yesterday the MySQL Daemons keep restarting every 7 mins or
so on one of my FreeBSD servers. The only work carried out recently
related to MySQL on this server was to temporarily disable replication
(its a slave) of one DB, and then re-enable it (via restore of data
and updati
24 matches
Mail list logo
