I've swapped my Mystic BBS from Windows to Linux (and from local to in cloud, due to a variety of issues), and things mostly work correctly, including incoming echomail.
However, I'm struggling with outgoing echomail and netmail. The logs
seem to be fine, the message base says, "Local Sent", but they're
clearly not going out. Or getting tossed at some point.
Anyone have experience with Mystic on Linux who can give me some ideas on what to try next? (I can probably give more useful set of details, but
I'm having difficultly figuring out what details would be of note.)
Have you set your node export type to crash instead of hold or other?
Good idea, though, perhaps sadly, my node export type was already set to crash.
Any other ideas?
Anyone have experience with Mystic on Linux who can give me some ideas
on what to try next? (I can probably give more useful set of details,
but I'm having difficultly figuring out what details would be of
note.)
I'm also having issues with Python, where it doesn't seem to do
anything, after getting around a different error message, but I think
I'll leave that issue for the future.
On 05-24-20 19:31, Adept wrote to All <=-
I've swapped my Mystic BBS from Windows to Linux (and from local to in cloud, due to a variety of issues), and things mostly work correctly, including incoming echomail.
However, I'm struggling with outgoing echomail and netmail. The logs
seem to be fine, the message base says, "Local Sent", but they're
clearly not going out. Or getting tossed at some point.
Anyone have experience with Mystic on Linux who can give me some ideas
on what to try next? (I can probably give more useful set of details,
but I'm having difficultly figuring out what details would be of note.)
I'm also having issues with Python, where it doesn't seem to do
anything, after getting around a different error message, but I think
I'll leave that issue for the future.
What do you see in your echomail\out directory?
☼ne thing to check is that you have zip installed. This is what happens when zip isn't installed.
☼ne thing to check is that you have zip installed. This is what happens when zip isn't installed.
I'm having trouble here to and I don't know what the problem is or what the solution will be.
Linux, you need to either have your mystic directory in the $PATH
variable or preface any call to an executable with "./". E.g. ./mutil export.ini I'd check your events first. This is probably the one that catches many out.
What happens when you run mutil manually? e.g. ./mutil export.ini (or whatever the .ini you are using for exporting mail is).
I haven't really done much with Python and Mystic.
--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Storm BBS (21:2/108)
However, I'm struggling with outgoing echomail and netmail. The logs
seem to be fine, the message base says, "Local Sent", but they're
clearly not going out. Or getting tossed at some point.
Anyone have experience with Mystic on Linux who can give me some ideas on what to try next? (I can probably give more useful set of details, but
I'm having difficultly figuring out what details would be of note.)
On 05-25-20 04:32, Adept wrote to Vk3jed <=-
Linux, you need to either have your mystic directory in the $PATH
variable or preface any call to an executable with "./". E.g. ./mutil export.ini I'd check your events first. This is probably the one that catches many out.
...that explains something that I've not known, or otherwise forgot,
with when to use the ./, so thank you for that.
Result DONE, 0 echo, 0 net, 0 skipped. But the log of an earlier
response does have Results: 1 echo, 0 net, 0 skipped, and looks pretty normal. So maybe it works and all, though I swear the logs weren't appreciably different.
I had worked through an earlier problem because of the lack of unzip, because the errors were obvious enough, but not so with zip, evidently.
I haven't really done much with Python and Mystic.
I probably wouldn't care too much but for some thematic things I had
done previously that don't currently work.
Though it's still nice for addons that other people have added.
On 05-25-20 03:20, Adept wrote to Al <=-
☼ne thing to check is that you have zip installed. This is what happens when zip isn't installed.
...and zip wasn't installed, so that very well may have been it. I apologize in advance if this is a dupe, but I'll send a response from
the quantum wormhole, too.
--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Storm BBS (21:2/108)
On 05-25-20 04:22, Adept wrote to Al <=-
☼ne thing to check is that you have zip installed. This is what happens when zip isn't installed.
I sent a response from Storm BBS, so hopefully that gets through, as
zip was, indeed, not installed. Thanks!
Also check you have ZIP installed else you will be seemingly creating a compressed packet to be sent but in fact not doing so.
On 25 May 2020, Avon said the following...
Also check you have ZIP installed else you will be seemingly creating compressed packet to be sent but in fact not doing so.
This seems to hang a lot of people up, myself included when I was first getting set up.
The logs don't seem to show an error if the archiver is missing. I'm wondering if it'd be possible to have that added, or maybe when you run mystic -cfg it can check to see whether zip & unzip are located in the mystic directory or somewhere in the path.
I may be a bit late to this one.
Also check you have ZIP installed else you will be seemingly creating a compressed packet to be sent but in fact not doing so.
Yeah, zip and unzip can bite you, if you're not aware of that. I usually install them anyway.
This seems to hang a lot of people up, myself included when I was first getting set up.
wondering if it'd be possible to have that added, or maybe when you run mystic -cfg it can check to see whether zip & unzip are located in the mystic directory or somewhere in the path.
I know you're not the author, just throwing the idea out there.
Well thanks for coming up with the correct answer anyway (And I'll probably poke around the settings to see if there's anything else of
note to be played with, now that I have a known-good setup.)
No probs, that's the only issue I find when replying to echomail that's some days old by the time I catch up the original poster has about 3-4 replies already with an answer.. :)
On 05-25-20 19:31, Adept wrote to Vk3jed <=-
Yeah, zip and unzip can bite you, if you're not aware of that. I usually install them anyway.
I found it odd - I don't have a whole lot of experience with starting
up bare bones linux things, and kinda assumed that zip and unzip would
be standard features rather than something that I installed.
But there's probably good reason not to include it.
On 05-25-20 14:27, Gluon wrote to Warpslide <=-
The problem is indeed how obfuscated the issue is. AFAIK there's no explicit check to see whether zip is installed, nor there is an error message logged. Instead you realise it is missing indirectly by
noticing messages aren't being packaged, nor coming out.
If Mystic were to be packaged as a Linux package, then this would be easily and seamlessly solved by declaring both zip and unzip as package dependencies. However, as a standalone software, the only solution is
in fact having the code itself checking/warning explicitly about those two. Obviously this is not something critical, but would help a lot of people, so I like your idea of discussing it.
☼ne thing to check is that you have zip installed. This is what happe when zip isn't installed.
...and zip wasn't installed, so that very well may have been it. I apologize in advance if this is a dupe, but I'll send a response from the quantum wormhole, too.
I think that's the bigger problem - not getting a clear error message
that zip is not installed.
On 05-25-20 09:25, Alpha wrote to Vk3jed <=-
This happens so often, to so many sysops (myself included), it would be great if Mystic could through some sort of error or warning in the log,
or during install, startup, etc. The way it does when Cryptlib isn't installed...
On 05-26-20 19:28, Adept wrote to Vk3jed <=-
After catching up with messages and seeing other people running into
the same issue, yeah, I suppose I'd second that. Even if it seems like something I might've entirely avoided if I had approached things differently.
Sysop: | echicken |
---|---|
Location: | Toronto, Ontario |
Users: | 2,224 |
Nodes: | 6 (0 / 6) |
Uptime: | 13:33:12 |
Calls: | 14,143 |
Files: | 295 |
Messages: | 551,295 |