CentOS 4.4 (64-bit) / 6.5.1 - need help

[Bailx]

i'm not sure what the deal is, but these are the errors i'm getting.

[Warning] Can't create test file /usr/local/slimserver/Cache/MySQL/localhost.lower-test
[ERROR] Can't start server: Bind on TCP/IP port: Permission denied
[ERROR] Do you already have another mysqld server running on port: 9092 ?
[ERROR] Aborting
[Note] /usr/libexec/mysqld: Shutdown complete
ERROR: MySQLHelper: createSystemTables() Couldn't connect to database: [Can't connect to local MySQL server through socket '/usr/local/slimserver/Cache/slimserver-mysql.sock' (2)]

i've tried quite a few things already... including all the obvious stuff, but... if anyone has any suggestions... i'll be happy to hear them.

[mherger]

> [ERROR] Can't start server: Bind on TCP/IP port: Permission denied

Are you running all this as root? You can't install or launch a service as
non-privileged user.

--

Michael

-----------------------------------------------------------------
http://www.herger.net/SlimCD - your SlimServer on a CD
http://www.herger.net/slim - AlbumReview, Biography, MusicInfoSCR

[Bailx]

yeah, I always use root... also this is a fresh install of CentOS.

i believe i had 6.5.0 working a few months ago... i didn't use 'build-perl-modules' that time though... i think i used cpan, or maybe it was from source i forget.

[Robin Bowes]

Bailx wrote:
> i'm not sure what the deal is, but these are the errors i'm getting.
>
> [Warning] Can't create test file
> /usr/local/slimserver/Cache/MySQL/localhost.lower-test
> [ERROR] Can't start server: Bind on TCP/IP port: Permission denied
> [ERROR] Do you already have another mysqld server running on port: 9092
> ?
> [ERROR] Aborting
> [Note] /usr/libexec/mysqld: Shutdown complete
> ERROR: MySQLHelper: createSystemTables() Couldn't connect to database:
> [Can't connect to local MySQL server through socket
> '/usr/local/slimserver/Cache/slimserver-mysql.sock' (2)]
>
> i've tried quite a few things already... including all the obvious
> stuff, but... if anyone has any suggestions... i'll be happy to hear
> them.


I seem to recall that this is a common problem on x86_64 - something to
do with library paths?

Try searching this forum.

R.

[Mark Miksis]

This has come up before, but I'm not sure we've ever gotten to the bottom of it. I seem to recall this problem more commonly on Ubuntu...

Did you install from RPM?
How are you starting slimserver?
Did you run build-perl-modules.pl without errors?

BTW, this is NOT the x86_64 mysql errmsg.sys path issue that I believe Robin is referring to. I suspect that you will not have that problem since the CentOS mysql-server version is sufficiently old.

[Bailx]

i've searched the forums plenty... i always do that first... and i tried a few of the things around, but nothing worked...

yes i installed from rpm...

i was starting slimserver from the /usr/local/slimserver dir

like this

./slimserver.pl

and like this

perl slimserver.pl

both with the same result...as could be expected i suppose...

i did not run build-perl-mudules without errors, i believe Compress::Zlib was in my error message at first, but I installed that through cpan and that error went away

maybe i'm wrong about having 6.5.0 working... maybe it was 6.3.x the last time i installed slimserver on my centos server...

[Mark Miksis]

i was starting slimserver from the /usr/local/slimserver dir

like this

./slimserver.pl

and like this

perl slimserver.pl

both with the same result...as could be expected i suppose...

Don't do this as root. The RPM creates a slimserver user and installs an init script. As root:

/sbin/service slimserver start

which will start the daemon with the slimserver user.

Also, if you have tried to run slimserver as root, it may have hosed the ownership of some files it creates. I suggest you delete the cache dir, /etc/slimserver.conf and /tmp/slimserver.log before running as above.

[Bailx]

yeah well... those weren't the normal ways i'd run it... it was the only way i could see an error message...

anyways... i deleted the 2 files you mentioned (even though they were owned by slim)

ran it like you said... which would be the same as registering it as a service and letting it start each boot (right?)

and having the same problem with it not working.... just no visible error message when ran in that fashion...

also... it does not re-create those 2 files.

...

man this used to be so easy to get running on rhel/clones... whats the deal?


thx for the help...

[Mark Miksis]

just no visible error message when ran in that fashion...

Any error (or other) messages in /tmp/slimserver.log?

[Bailx]

i guess it's not getting that far, because there is no error log in /tmp or in /var/log .... or anywhere else for that matter. find / -name slimserver.log = nada