Somehow broke logger, thereby breaking everything

Hi

Could I have it as well please?

Cheers!

PS. Maybe you could post some pointers about compiling it on our own :)

Hello,
I'm also having the same problem when trying to start MySQL... could someone please send me the (compiled) logger file? I'm rather new at this, so it would be great if you could add some pointers as well. :-)

Thank's in advance!
// Marina

I have same problem. Would someone please send to me the fixes logger file? :D

Got the same issue.
Could you send me a copy, or link to a download :)

I tried to download the latest BusyBox stable, and the logger didn't have any -i option?
Which logger do you actually need (use by default)?

May I have the compiled logger as well?

Hi All,

I got an NVX a couple of weeks ago, promised myself I would behave, but I just could not resist... I had to tinker with it! :D

I got hit by the same logger problem, but I choose a "less drastic" way of getting around it.
Sharing with the world so you have another option, and may choose not to touch the installed software (busybox).

I replaced the /usr/bin/logger symlink to busybox (cd /usr/bin/; rm -i logger; vi logger; #A, copy & paste, ESC : x ; chmod +x logger) by the following script:

#!/bin/bash
while getopts ":st:p:" Option
do
  case ${Option} in
        s | t | p ) cmdline="${cmdline} -${Option} ${OPTARG}" ;;
  esac
done
shift $((${OPTIND} - 1))

busybox logger "${cmdline}" "${*}"

This way the -i parameter is ignored, for mySQL and other scripts that try to call busybox/logger with it.

Regards,

b

Can I please get a copy of this logger file, I am having the same problem. Many thanks

-Mike

EDIT: Nevermind, the above post worked for my problem, thanks!

I have a NV+ and I'm getting the Invalid option -- i on the logger. Can someone send me a replacement logger that will work on my NV+?

Thanks.

Well I have PM-ed this to bsilva, but probably can post it here as well, maybe it will help other people too:

Hi BSilva,

I read your post on readynas.com, thanks for sharing! As a totally new linux-user, I tried to figure out what you meant with it. However, I think I figured it out.
You say you have to do this:

NAS:/usr/bin#cd /usr/bin/ -> go to directory /usr/bin/
NAS:/usr/bin#rm -i logger -> remove the logger symlink - don't know exactly what a symlink is, but I did this step
NAS:/usr/bin#vi logger -> open the logger application with vi-editor - creates a new file
In the vi-application press:
A -> go in the file
Copy & paste -> copy and paste the script you posted
Esc:x -> save and quit Vi
NAS:/usr/bin#chmod +x logger -> set the correct file permission

I did all of these steps, resulting in your bash-script being in the /usr/bin/logger file.
Now I execute:
NAS:/usr/bin#/etc/init.d/mysql -start

And now I don't get an error anymore about the logger, but I only see:

"Starting MySQL database server: mysqld . . . . . . . . . . . . failed!"

I read on another forum that you then need to check /var/log/syslog, I did this and here I see:
Dec 6 20:07:35 NAS1 root: -p daemon.err -t /etc/init.d/mysql -p daemon.debug

I have no idea what to do next. And I really don't know why everything is this difficult in Linux I only want to install php 5.3 and mysql, so I can start programming my sites again, but I'm already busy with installing *** 2 basic and very popular programs for almost 2 days! (maybe it is because I have debian etch?)

Well sorry for the last part, I'm really sad about this, because it takes this much time. However, its people like you that give people solutions why I keep trying. So thanks for that!

Peter

Hi Peter,

Just replied your MP and sent you the correct logger file (the one which works on my ReadyNas Pro);

I've read your previous message and maybe the problem is just a "permissions" problem. MySQL needs to create some files into some directories (usually 'mysqld.pid' and 'mysqld.sock'). Don't know exactly where on your ReadyNas product, so check the logs file to find out where you must fix theses permissions;

Remember, Mysql daemon uses the "admin" user to start, so you must be sure that "admin" user can write into thoses directories.

@++
Dwarf