Strange show stopper error on installed scalr server

[Srini]

Once my scalr server runs for a day or so, instance always remained in a pending state.  After trouble shooting various touch points, I finally figured out it is a strange issue with MySQL.

Here is what happens:

1. The message sent from the scalarizr on the instance is received by the scalr server.
2. The message is also logged in the syslog table.
3. The control queue handler runs an insert statement on the database table messages.
4. The insert is successful and there is no exception, BUT the data is not present in the messages table!

I ran phpmysqladmin and connected to the database. Then ran the sql statement to insert the data. A successful message was displayed and row id was displayed. However the DATA WAS NOT IN the table, select * returned empty table.

I then restarted mysqld and everything was fine! The issue seems to be inserts into the messages table are not succeeding for some reason once mysqld has been running for some time (typically overnight)

My setup: Centos 5.6, PHP 5.3.10 and MySQL 5.5.20 (I got the php from the remi repo and the mysql-libs from remi have a dependency on mysql5 from the remi repo, so had to install the mysql 5.5 server from there)

The my.cnf file had minimum settings as below:

------------------------------------------
[mysqld]
user=mysql

datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

--------------------------------------------------------------------------

Any ideas? Thanks for your help on this, really appreciate it.  Unless I fix this I am stuck :(

Cheers
Srini

[Igor Savchenko]

Srini,

Scalr was never tested on MySQL 5.5 . This mentions in our wiki -
scalr requires MySQL 5.1.X. Maybe this is an issue.

Regards,
Igor

> --
> You received this message because you are subscribed to the Google Groups
> "scalr-discuss" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/scalr-discuss/-/XCr2cBaVcFgJ.
> To post to this group, send email to scalr-...@googlegroups.com.
> To unsubscribe from this group, send email to
> scalr-discus...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/scalr-discuss?hl=en.

[Srinivasan Subramanian]

Hi Igor

I also thought so. Since I could not get the combination of php-5.3.x and
mysql 5.1, I compiled php 5.3.10 from source.

I am now stuck with one last issue and if you can help, it will be great.

php-posix is enabled. However functions like setsid etc are not available
and exception is thrown. When I checked the compilation of PHP, the
./configure output says setsid not found. The AC_CHECK_FUNCTION is failing
for setsid and some other functions.

I have hunted high and low but am unable to figure out what I need to
install to enable the posix setsid and other functions.

Any ideas or suggestions?

Regards
Srini

[Srini]

Hi Igor

Realized that and finally now reinstalled with MySQL 5.1.  Will check for a couple of days and let you know.

The > PHP 5.3.5 and MySQL 5.1 installation is a nightmare as ready RPMs are not available (PHP 5.3.x are mostly with MySQL 5.5).  I finally compiled everything from source and it looks to be running now.

Will post the results in a couple of days if things have improved :)

Thanks

Srini

On Thursday, March 15, 2012 5:30:38 PM UTC+5:30, DicsyDel wrote:

Srini,

Scalr was never tested on MySQL 5.5 . This mentions in our wiki -
scalr requires MySQL 5.1.X. Maybe this is an issue.

Regards,
Igor

> scalr-discuss+unsubscribe@googlegroups.com.

[Srinivasan Subramanian]

Hi Igor

The problem was not MySQL 5.1 or 5.5 (I am now running it on 5.1).

My test scalr installation is an "All-in-one" server running apache, cron
and database. The default scalr setup sets log messages to INFO and I ran
it without changing that. At the end of a few hours, the syslog table
already has thousands of entries and in the limited setup I was doing the
mysql daemon went into an indeterminate state.

I have now set logging to WARN and the server is running without any issues.
Important hint for all self installed scalr nodes, either have a monster
mysql instance if you want INFO messages or set it to WARN.

Thanks for all your help and interest in helping out on this.

Cheers
Srini

-----Original Message-----
From: Igor Savchenko
Sent: Thursday, March 15, 2012 5:30 PM
To: scalr-...@googlegroups.com
Subject: Re: Strange show stopper error on installed scalr server