Page 1 of 2
run Command on Debian always cause Problem
Posted: 04 Jan 2015, 09:04
by Mirery
Every time i use the ./run command on Linux i get this Error in runtime.log
/run: Zeile 109: /usr/bin/php
: Datei oder Verzeichnis nicht gefunden
I checked the run.ini nearly 100 times the Code is:
; config the path to your php executeable here
phpPath=/usr/bin/php
; do not remove this line!
and that's the Path of the PHP Executable... If i use the run_console command it's all working perfect.
The Source is the 0.9.7 expandion (i updatet ingame to 0.9.8.1) but that also doesn't change anythink about that.
Re: run Command on Debian always cause Problem
Posted: 04 Jan 2015, 13:07
by reaby
I remember the linux starter was having problems in the past too, that time it was having wrong line-endings.
it had \r\n instead of \n which made the starter not working right.
Hopefully it isn't the same problem again with the run.ini or the run-file again.. Have to say, I'm not very good with Linux, as I only have used Ubuntu (and a little bit Debian). Personally in Linux I tend to run the script and the dedicated in a screen-session so I see the console messages for debugging...
If someone is really good with linuxes and knows a way to do a generic starter that starts the script in background... just let me know or post a proposed starter script at this topic
Proposed fix for now
easiest one is to:
1) use ./run_console and type
ingame chat
2) start screen, create a new screen window and start the script using ./run_console
Re: run Command on Debian always cause Problem
Posted: 04 Jan 2015, 13:20
by Mirery
Yeah i'm using the screen Version for now i just want to say that there's something wrong with Line 109 in run
Code: Select all
$PHP $PWD/bootstrapper.php $ARGS </dev/null > $PWD/logs/runtime.log 2>&1 &
That's the Line that cause the Error
And btw:
reaby wrote:
easiest one is to:
1) use ./run_console and type
ingame chat
This will just close expansion and not restart it. There is no Error in runtime.log then but it don't restart!
Re: run Command on Debian always cause Problem
Posted: 04 Jan 2015, 14:22
by reaby
Mirery wrote:
And btw:
reaby wrote:
easiest one is to:
1) use ./run_console and type
ingame chat
This will just close expansion and not restart it. There is no Error in runtime.log then but it don't restart!
Well all I can say is that it works for me! I double checked it.
Maybe your servers config is not allowing php to run exec.
Mirery wrote:It's just annoying to follow the instruction on Wiki and nothing works...
Luckily I saw this before you edited the message, other-vice I wouldn't know this issue!
So, thanks for informing about this, there has been no discussion about the current wiki instructions doesn't work...
and trust me I know the feeling, it's damn annoying when you see cool project and the documentation is running for old releases and you don't get it running, all you encounter is just errors.. it frustrates.
But, as Oliver and I do this as a hobby and writing documentation is boring compared to coding...
so let there be another todo item for the todo-list then
Re: run Command on Debian always cause Problem
Posted: 04 Jan 2015, 14:29
by undef.de
Convert "\r\n" with
dos2unix.
Run PHP without a php.ini with "/usr/bin/php -n ".
Re: run Command on Debian always cause Problem
Posted: 04 Jan 2015, 15:19
by reaby
Hmm... Running php without the php.ini is maybe not a good solution, since the extensions are not loaded then ?
Re: run Command on Debian always cause Problem
Posted: 04 Jan 2015, 15:30
by w1lla
Re: run Command on Debian always cause Problem
Posted: 04 Jan 2015, 15:48
by Mirery
Will cause this:
golf995:~# /usr/bin/php5 -n /root/eXpansion-0.9.7/bootstrapper.php
_| _| _| _| _|
_|_| _|_| _|_|_| _|_|_| _|_|_| _| _| _| _|_|
_| _| _| _| _| _| _| _| _| _| _| _| _| _| _|_|_|_|
_| _| _| _| _| _| _| _| _| _| _| _| _| _|
_| _| _|_|_| _| _| _| _|_|_| _|_|_|_| _| _| _|_|_|
-----------------------------------------------------
PHP Environment Compatibility Test
-----------------------------------------------------
PHP 5.3.1 or newer -> required -> [ Yes ] 5.4.35-0+deb7u2
Standard PHP Library -> required -> [ Yes ]
JSON -> required -> [ Yes ]
cURL with SSL -> required -> [ No ]
MySQL -> optional -> [ No ]
SQLite3 -> optional -> [ No ]
-----------------------------------------------------
You should install cURL PHP extension
on debian/ubuntu : sudo apt-get install php5-curl
Your system is not compatible, check your php configuration.
So it can't find php5-curl then (it's installed!!!)
If I use
Code: Select all
/usr/bin/php5 /root/eXpansion-0.9.7/bootstrapper.php
Everything is fine...
Re: run Command on Debian always cause Problem
Posted: 04 Jan 2015, 15:54
by Mirery
And perhaps i just missunderstand the Instruction....
./run --start should usually start Manialive or?
I just get this:
golf995:~/eXpansion-0.9.7# ./run --start
Launching ManiaLive Daemon with the following arguments:
Writing process id : 4892 to file.
If i add anything else behind the Command for example:
golf995:~/eXpansion-0.9.7# ./run test --start
Launching ManiaLive Daemon with the following arguments: test
Writing process id : 5037 to file.
But ManiaLive isn't starting at all and nodaemon cause this:
golf995:~/eXpansion-0.9.7# ./run --nodaemon
Launching ManiaLive with the following arguments:
: Datei oder Verzeichnis nicht gefunden
Re: run Command on Debian always cause Problem
Posted: 04 Jan 2015, 15:55
by w1lla
did you restart apache2?