[Reso] Server won't start: ./lshttpd: 1: Syntax error: "(" unexpected (expecting ")")

[snowweb]

I've just installed the free version of lightspeed on my DNS-323 NAS which is runnng a hacked firmware and fun_plug linux distro. I'm trying to replace lighttpd.

The install went smoothly, but when I try to start the server, I get:

root@IN07:~# /mnt/HD_a2/ffp/installed-programs/lightspeed/bin/lswsctrl start
./lshttpd: 1: Syntax error: "(" unexpected (expecting ")")
[ERROR] Failed to start lshttpd!
killall: lshttpd: no process killed
./lshttpd: 1: Syntax error: "(" unexpected (expecting ")")
[ERROR] Failed to start lshttpd!

I don't know where to start looking to trouble shoot this. Any help would be great.

Thanks,

peter

 

[mistwang]

The shell script is not compatible with the shell of the linux in your NAS, can you install bash?
You can ignore the lswsctrl script, just run lshttpd directly.

 

[snowweb]

Thanks mistwang. I've installed bash and tried again, I get the same result

I echoed the bash version for you.

root@IN07:~# echo $BASH_VERSION
3.2.33(1)-release
root@IN07:~# /mnt/HD_a2/ffp/installed-programs/lightspeed/bin/lswsctrl start
./lshttpd: line 1: syntax error: "(" unexpected (expecting ")")
[ERROR] Failed to start lshttpd!
killall: lshttpd: no process killed
./lshttpd: line 1: syntax error: "(" unexpected (expecting ")")
[ERROR] Failed to start lshttpd!

Any more ideas please?

Thanks!

 

[mistwang]

just try running lsws/bin/lshttpd directly, check log files under lsws/logs/

 

[snowweb]

Thanks mistwang for your replies. Sorry I forgot to add what happened when I ran lshttpd directly. This is what happened:

root@IN07:~# /mnt/HD_a2/ffp/installed-programs/lightspeed/bin/lshttpd start
-bash: /mnt/HD_a2/ffp/installed-programs/lightspeed/bin/lshttpd: cannot execute binary file

I checked /mnt/HD_a2/ffp/installed-programs/lightspeed/logs/ and the directory is empty.

Thanks for helping me.

peter

 

[NiteWave]

-bash: /mnt/HD_a2/ffp/installed-programs/lightspeed/bin/lshttpd: cannot execute binary file

what's the output of

#ls -al /mnt/HD_a2/ffp/installed-programs/lightspeed/bin/lshttpd

?

it should be 555. if not, run

#chmod 555 /mnt/HD_a2/ffp/installed-programs/lightspeed/bin/lshttpd

 

[snowweb]

Thanks Nitewave.

I ran the command you said:

root@IN07:~# ls -al /mnt/HD_a2/ffp/installed-programs/lightspeed/bin/lshttpd
lrwxrwxrwx 1 root root 16 May 9 13:33 /mnt/HD_a2/ffp/installed-programs/lightspeed/bin/lshttpd ->
./lshttpd.4.0.14

Is that right?

peter

 

[snowweb]

One other thing, I checked the permissions on /mnt/HD_a2/ffp/installed-programs/lightspeed/bin/lshttpd.4.0.14 which is what lshttpd points to. They are 555.

The permissions on the /mnt/HD_a2/ffp/installed-programs/lightspeed/bin/ directory are 755 as is the lightspeed directory.

 

[NiteWave]

is your OS 32-bit or 64-bit?

#file /bin/ls
or
#uname -a

then how about lshttpd?

#file /mnt/HD_a2/ffp/installed-programs/lightspeed/bin/lshttpd.4.0.14

 

[snowweb]

is your OS 32-bit or 64-bit?


then how about lshttpd?

Sorry, not sure, although I'd be surprised if a DNS-323 is 64 bit. Is there a command I can run to find out for sure?

What did you mean by the two quotes you included please?

Thanks,

Peter

 

[NiteWave]

run those commands on your server to determine 32-bit or 64-bit.
post the output here.

 

[snowweb]

root@IN07:~# uname -a
Linux IN07 2.6.12.6-arm1 #31 Thu Mar 26 18:20:41 CST 2009 armv5tejl GNU/Linux

root@IN07:~# file /mnt/HD_a2/ffp/installed-programs/lightspeed/bin/lshttpd.4.0.14
/mnt/HD_a2/ffp/installed-programs/lightspeed/bin/lshttpd.4.0.14: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux
2.2.5, dynamically linked (uses shared libs), not stripped

Thanks

 

[NiteWave]

so this is what you said DNS-323 NAS:
http://wiki.dns323.info/

and its processor(CPU):
http://en.wikipedia.org/wiki/ARM_architecture

lsws no build for ARM processor yet. so the binary you downloaded for x86 CPU can't run on it.

 

[snowweb]

Oh! That's a shame. Thanks for your help identifying the problem anyway. I'd never of figured that out myself.

Maybe I'll stop back here next year and see if you support my processor then. Many thanks anyway.

peter