#3 MUTIL fails upon importing messages

[Flavio Bessa]

When running mutil with the corresponding .ini file to import FTN-style packets into the message base, the following errors can be seen:

caution: filename not matched: tempftn
caution: filename not matched: temputil
caution: filename not matched: text

Then MUTIL exits with RESULT DONE, but checking the logs it can be seen that the FTN packets have not been imported properly.

[Flavio Bessa]

Essentially, you can see the following error messages when running mutil:

  unzip:  cannot find zipfile directory in one of /opt/guardian/echomail/in/00000002.mo0 or
                                                                /opt/guardian/echomail/in/00000002.mo0.zip, and cannot find /opt/guardian/echomail/in/00000002.mo0.ZIP, period.

But, if you look, it is there:

flbessa@ubuntu:/opt/guardian/echomail/in$ ls -la
total 816
drwxr-xr-x 2 root root 4096 Mar 7 08:45 .
drwxr-xr-x 4 root root 4096 Feb 26 16:55 ..
-rw-r--r-- 1 root root 58183 Mar 3 23:06 00000002.fr0
-rw-r--r-- 1 root root 295771 Apr 8 09:11 00000002.mo0
-rw-r--r-- 1 root root 55609 Mar 4 23:48 00000002.sa0
-rw-r--r-- 1 root root 119122 Mar 5 23:32 00000002.su0
-rw-r--r-- 1 root root 7705 Feb 26 23:46 00000002.su1
-rw-r--r-- 1 root root 82032 Mar 2 15:25 00000002.th0
-rw-r--r-- 1 root root 39424 Mar 2 23:16 00000002.th1
-rw-r--r-- 1 root root 74290 Feb 28 23:47 00000002.tu0
-rw-r--r-- 1 root root 73275 Mar 1 23:32 00000002.we0
flbessa@ubuntu:/opt/guardian/echomail/in$

[Flavio Bessa]

Please find attached the scripts I am using for importing and exporting messages.

[Vincent Chapman]

Sorry for the delayed response. I do not believe this is a software problem.

The reason the packages are not imported is that you do not have permission to write to that folder.

The directory listing you posted also shows username in the prompt, which is very helpful in rapidly diagnosising the problem. If you review the permissions, as displayed by the ls -la command, the BBS is installed as root, the current default install. To run the BBS under a different user, first make a guardian group

$ sudo add flbessa guardian

then change permission for flbessa to access guardian. This BBS was ported origially from the microsoft world, and the error messages may not correcly reflect permission problems.

$ chown -R root.guardian /opt/guardian
$ chmod -R g+w /opt/guardian

This will allow you to run any parts of guardian under root or flbessa. Please understand, it is probally necessary to run the chown -R command on the /opt/guardian folder each time you make changes. The last option is you could create a guardian user and then run the BBS under guardian and use the su command to change to guardian before doing maintence. This is the only way to guarantee no permissions problems. If you do not wish to change any permissions at all, then sudo -s to root and then admin the BBS.

Unix permissions are:

-rw-r--r-- 1 root root 73275 Mar 1 23:32 00000002.we0 (one of your files)

r - read
w - write
x - execute

ls shows owner then group then other. The ower of the file is root and the group is root.

owner (root): read and write
group (root): read
other: read

[Flavio Bessa]

Hello,

I did the changes and the issue continues.

When running under flbessa:

An unhandled exception occurred at $0000000000400C68 :
EInOutError : Access denied
$0000000000400C68

When running under sudo:

                                               unzip:  cannot find zipfile directory in one of /opt/guardian/echomail/in/00000002.mo0 or
                                                                /opt/guardian/echomail/in/00000002.mo0.zip, and cannot find /opt/guardian/echomail/in/00000002.mo0.ZIP, period.

[Flavio Bessa]

drwxrwxr-x 2 root guardian 4096 Dec 28 05:48 localqwk
drwxrwxr-x 2 root guardian 4096 Mar 7 08:14 logs
-rwxrwxrwx 1 root guardian 16735 Mar 7 08:15 mailin.ini
-rwxrwxrwx 1 root guardian 16744 Feb 26 17:09 mailout.ini
-rwxrwxr-x 1 root guardian 48720 Mar 7 06:06 maketheme
drwxrwxr-x 2 root guardian 4096 Feb 26 16:55 menus
-rwxrwxr-x 1 root guardian 194448 Mar 7 06:06 mide
-rwxrwxr-x 1 root guardian 542832 Mar 7 06:06 mis
-rwxrwxr-x 1 root guardian 117824 Mar 7 06:06 mplc
drwxrwxr-x 2 root guardian 4096 Mar 2 05:43 msgs
-rwxrwxrwx 1 root guardian 457328 Mar 7 06:06 mutil
-rwxrwxr-x 1 root guardian 16745 Dec 28 05:48 mutil.ini
-rwxrwxr-x 1 root guardian 244 Dec 28 05:48 mutil.toplist.template.txt
-rwxrwxr-x 1 root guardian 241536 Mar 7 06:06 nodespy
-rwxrwxr-x 1 root guardian 403 Dec 28 05:48 nodespy.ini
-rwxrwxr-x 1 root guardian 402784 Mar 7 06:06 qwkpoll
drwxrwxr-x 2 root guardian 4096 Feb 26 16:55 scripts
drwxrwxr-x 2 root guardian 4096 Dec 28 05:48 semaphore
drwxrwxr-x 2 root guardian 4096 Mar 2 05:46 temp0
drwxrwxr-x 2 root guardian 4096 Apr 8 09:49 temp1
drwxrwxr-x 2 root guardian 4096 Feb 26 17:04 tempftn
drwxrwxr-x 2 root guardian 4096 Mar 7 08:14 temputil
drwxrwxr-x 2 root guardian 4096 Mar 8 07:15 text

[Flavio Bessa]

Hello,

At the end of the day the issue was not related to permissions. I managed to fix it after comparing the "Archive Editor" with the official Mystic release, then I realized that the zip/unzip commands were lacking quotation marks where the %1 and %2 parameters were. Upon fixed this, the issue was solved.