ioNiNJA Fatal error script

[Stars]

Hi,

I keep getting an error when i run a command like site resort / rescan mp3

site resort mp3 if I do i get this error

[L] 200-Reading: F:/-1) Mp3/incoming/0518
[L] 550 Command failed (script): Fatal script error.

i have this version ioNiNJA:
ioNiNJA.BETA.Stable.v0.8.9.6-2009-06-29

and version ioFTPD:
ioFTPD v7.7.2

I hope someone can help my

Regards Stars

[Yil]

You can goto the /logs directory and look at the SystemError.log file which should show you the details about TCL script errors which would give us something to go on.

Did this work before for you and you just upgraded ioFTPD and it stopped working? In ioFTPD v7.7.x the /lib directory was upgraded but you had to take some care to keep the nxtools/ioninja parts of that directory when upgrading it. It's possible you missed something there if it was working fine before. In fact, I anticipated this as a problem and ioFTPD now actually checks for the version of the /lib dir that it needs and won't start if something is wrong, but it doesn't do this for scripts. They would just fail with fatal script errors like you are seeing. This should be obvious from the error log files though.

[Stars]

05-24-2011 11:19:58 "..\scripts\ioNiNJA\ioNiNJA.itcl" terminated abnormally
--- ErrorInfo ---
couldn't compile regular expression pattern: parentheses () not balanced
while executing
"regsub -nocase $basedirs $dir $pwd"
(procedure "::ioNiNJA::resort" line 14)
invoked from within
"::ioNiNJA::resort "
("RESORT" arm line 1)
invoked from within
"switch -- [lindex $args 0] {
SYMCLEAN {
set temp [userfile open [resolve uid [lindex [user list] 0]]]
set temp [mountfile open ../etc/defaul..


This is one of my error

I have an new install ioftpd with ioioNiNJA

When i upload new files to the server then it works sort sctipt

Regards

[Yil]

That sounds like a question best left answered by o_dog. However I'm sure the first thing you should try is to use the default ioNinja configuration to make sure you haven't goofed when editing the config file... My guess is something you modified isn't happy, in fact I bet it might be a quoting problem with ()'s in that regular expression.

Also, just in case this is an issue, can you confirm this is a simple alphanumeric directory path both in the VFS and on disk? No ()'s or other things that might confuse things.

[Stars]

Thnx :)

I have change F:/-1) Mp3/incoming/ to F:/00-Mp3/incoming/ and works fine now.

There was an problem with -1)

Thnx :D

[Yil]

If the problem was with the path, you can maybe fix the problem by using this change...

regsub -nocase -- $basedirs $dir $pwd

That extra -- in there tells the command to stop trying to look for arguments which should make it avoid the error.