Hi All,

I just noticed something very interesting. While I was logged on to node 1
here on CRBBS, I had someone else log into the board. They were also showing
as being on node 1.

The node1.log file is very segmented, as it shows an entry whenever an online person does something, or someone attempts to log on... In the following log segment, I was logged in the entire time on node 1.

-=-=-=-=-=-=-=-=

------------------- Node 1 (Mystic v1.12 A35)
2017.09.21 11:37:39 Connect from 177.34.152.152(b1229898.virtua.com.br) 2017.09.21 11:46:57 Scan for new messages
2017.09.21 11:48:15 Scan for new messages
2017.09.21 11:48:19 Scan for new files
2017.09.21 11:49:30 Scan for new messages

------------------- Node 1 (Mystic v1.12 A35)
2017.09.21 11:49:54 Connect from 67.61.21.181 (67-61-21-181.cpe.cableone.net) 2017.09.21 11:49:59 Randall Flagg logged in
2017.09.21 11:50:02 Scan for personal messages
2017.09.21 11:50:27 Executed Door: /home/dan/doors/gdyn2/gdyn.sh /home/dan/mystic/temp1/DORINFO1.DEF 1

------------------- Node 1 (Mystic v1.12 A35)
2017.09.21 11:53:51 Connect from 201.0.62.172 (201-0-62-172.dsl.telesp.net.br)

------------------- Node 1 (Mystic v1.12 A35)
2017.09.21 11:54:42 Connect from 193.150.84.131 (Unknown)

------------------- Node 1 (Mystic v1.12 A35)
2017.09.21 11:55:20 Connect from 193.150.84.131 (Unknown)

------------------- Node 1 (Mystic v1.12 A35)
2017.09.21 11:55:58 Connect from 193.150.84.131 (Unknown)

------------------- Node 1 (Mystic v1.12 A35)
2017.09.21 11:56:27 Connect from 217.77.221.133 (static-217-77-221-133.wildpark.net)
2017.09.21 11:57:12 Executed Door: /home/dan/doors/gdyn/gdyn.sh /home/dan/mystic/temp1/DORINFO1.DEF 1
2017.09.21 11:57:53 Executed Door: /home/dan/doors/forhonour/fh.sh /home/dan/mystic/temp1/DORINFO1.DEF 1
2017.09.21 12:00:33 User logged off
2017.09.21 12:00:46 Scan for new messages


---

Black Panther
aka Dan Richter
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

On 09/21/17, Black Panther said the following...

I just noticed something very interesting. While I was logged on to node
1 here on CRBBS, I had someone else log into the board. They were also showing as being on node 1.

I've just noticed another issue, that I believe could be linked to the previous...

While lookin at the /mystic/logs directory, I noticed I have over 1100 files currently residing there... I have the regular fidopoll.log, node1.log, etc, but I also now have fidopoll[conflicted].log, node1[conflicted].log, node1[conflicted1044].log, etc.

I'm not sure what's causing these 'conflicted' log files, but it's a bit annoying to have that many files in that directory. While some of them are
only a few bytes, others are MB in size...

Anyone else seen this happen before?

Thanks,


---

Black Panther
aka Dan Richter
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

files currently residing there... I have the regular fidopoll.log, node1.log, etc, but I also now have fidopoll[conflicted].log, node1[conflicted].log, node1[conflicted1044].log, etc.

Dan;
I'm not seeing that in 1.12 A34... I've not upgraded to A35 yet so I can watch / see what happens with others that have.
I've not ever seen that happen. Looks like something that g00r00 should
look into because I've noticed people having issues such as ghost logins, needing to kill connections etc...

Gary

----=[ Gary Crunk * Another F-ing BBS * anotherbbs.bbsindex.com ]=----

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: Another F-ing BBS (21:2/105)

Dan;
I'm not seeing that in 1.12 A34... I've not upgraded to A35 yet so I
can watch / see what happens with others that have.
I've not ever seen that happen. Looks like something that g00r00
should look into because I've noticed people having issues such as ghost logins, needing to kill connections etc...

I'm having these problems, and my system locking up with mystic chewing up my processor.

I may considering down grading until there is a fix.

--- Mystic BBS v1.12 A35 (Linux/32)
* Origin: Clutch BBS * telnet://clutch.darktech.org (21:1/199)

On 09/26/17, Black Panther pondered and said...

I've just noticed another issue, that I believe could be linked to the previous...

While lookin at the /mystic/logs directory, I noticed I have over 1100 files currently residing there... I have the regular fidopoll.log, node1.log, etc, but I also now have fidopoll[conflicted].log, node1[conflicted].log, node1[conflicted1044].log, etc.

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

I have not seen/heard of this issue before. No similar things with other OS versions that I am aware of Dan. It sounds like a file permissions thing to
me. Something was created but then not correctly deleted or released?

Best, Paul

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 09/27/17, Avon said the following...

While lookin at the /mystic/logs directory, I noticed I have over 110 files currently residing there... I have the regular fidopoll.log, node1.log, etc, but I also now have fidopoll[conflicted].log, node1[conflicted].log, node1[conflicted1044].log, etc.

I have not seen/heard of this issue before. No similar things with other OS versions that I am aware of Dan. It sounds like a file permissions thing to me. Something was created but then not correctly deleted or released?

I'm still not sure what caused them. I have downgraded to A34 for now, in
hopes that might help.

The /mystic/logs directory is over 1730 files right now... I also noticed
that the chat1.dat file in the /mystic/data directory was also getting the conflicted issues as well. There are over 800 of those, along with about 100
of the chat2.dat file...

I think I'm going to archive the entire log directory and let it recreate all of the logs. I hope the issue stops with the use of A34. I know I didn't have this issue with it before...


---

Black Panther
aka Dan Richter
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A34 (Linux/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

On 09/27/17, Black Panther pondered and said...

I'm still not sure what caused them. I have downgraded to A34 for now, in hopes that might help.

The /mystic/logs directory is over 1730 files right now... I also noticed that the chat1.dat file in the /mystic/data directory was also getting
the conflicted issues as well. There are over 800 of those, along with about 100 of the chat2.dat file...

I think I'm going to archive the entire log directory and let it
recreate all of the logs. I hope the issue stops with the use of A34. I know I didn't have this issue with it before...

Yes that seems weird to me and if it's happening across a number of
directories etc. then I am suspicious about something to do with file locking
/ permissions that might be in play. g00r00 will be interested no doubt when
he next has some time to play with Mystic :)

It's that darn thing called real life commitments that keep getting in the
way. In my case I'd keep typing now but I have to dash off and make cup of
tea number three for the lady in my life :)

Best, Paul

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 09/27/17, Avon said the following...

The /mystic/logs directory is over 1730 files right now... I also not that the chat1.dat file in the /mystic/data directory was also gettin the conflicted issues as well. There are over 800 of those, along wit about 100 of the chat2.dat file...

Yes that seems weird to me and if it's happening across a number of directories etc. then I am suspicious about something to do with file locking / permissions that might be in play. g00r00 will be interested
no doubt when he next has some time to play with Mystic :)

It does seem weird. I was also thinking about file locking being the
culprit... I do believe that Mystic allowing multiple users to be on the same node has a big part of it. I'm sure that is Mystics way of appending to the logs and chat1.dat file, with multiple users.

The only thing that has me confused, (well, one of them... lol) is the fact that it was happening to the server_events.log and fidopoll.log as well...

I'm monitoring the status of the log files with A34, and we'll see what happens.


---

Black Panther
aka Dan Richter
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A34 (Linux/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

On 09/27/17, Black Panther pondered and said...

directories etc. then I am suspicious about something to do with file locking / permissions that might be in play. g00r00 will be intereste no doubt when he next has some time to play with Mystic :)

It does seem weird. I was also thinking about file locking being the culprit... I do believe that Mystic allowing multiple users to be on the same node has a big part of it. I'm sure that is Mystics way of
appending to the logs and chat1.dat file, with multiple users.

Is that right? I'm not sure it is. When you say multiple users on the same
node I don't think that's the case. Sure multiple users on different nodes
but I have never seen more than one user on a node at any one time. Perhaps I misunderstand?

The only thing that has me confused, (well, one of them... lol) is the fact that it was happening to the server_events.log and fidopoll.log as well...

Yeah, and when that sort of thing is happening it speaks to me as if it were
a wider issue spanning all of the directory etc. file locking, permissions issues etc.

Not sure but that was my best guess :)

I'm monitoring the status of the log files with A34, and we'll see what happens.

I have this vision of you watching a computer with a clip board now :-p

Best, Paul

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 09/27/17, Avon said the following...

Is that right? I'm not sure it is. When you say multiple users on the
same node I don't think that's the case. Sure multiple users on
different nodes but I have never seen more than one user on a node at
any one time. Perhaps I misunderstand?

Yup. If I am online on node 1, and another user, let's just say Andrew logs
in to the board, he will also be on node 1. If I take a look at nodespy, it will bounce between showing one user then the other. It's whenever the online status changes, such as changing menus. Nodespy will show Black Panther
Reading messages, then change to Apam Viewing files, then change back to
Black Panther viewing message menu, etc...


---

Black Panther
aka Dan Richter
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A34 (Linux/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

On 09/27/17, Black Panther pondered and said...

Yup. If I am online on node 1, and another user, let's just say Andrew logs in to the board, he will also be on node 1. If I take a look at nodespy, it will bounce between showing one user then the other. It's whenever the online status changes, such as changing menus. Nodespy will show Black Panther Reading messages, then change to Apam Viewing files, then change back to Black Panther viewing message menu, etc...

That's seriously weird :)

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Yup. If I am online on node 1, and another user, let's just say Andrew logs in to the board, he will also be on node 1. If I take a look at nodespy, it will bounce between showing one user then the other. It's whenever the online status changes, such as changing menus. Nodespy will show Black Panther Reading messages, then change to Apam Viewing files, then change back to Black Panther viewing message menu, etc...

Oh crap. Did I break your BBS?


--- MagickaBBS v0.7alpha (Linux/x86_64)
* Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)

On 09/27/17, Avon said the following...

Yup. If I am online on node 1, and another user, let's just say Andre logs in to the board, he will also be on node 1. If I take a look at nodespy, it will bounce between showing one user then the other. It's

That's seriously weird :)

It sure is...

It does seem to be only an issue with A35 though. Right now, I'm on node 1,
and I have another user online, and they are showing as being on node 2. I
hope this means it's not going to be an issue anymore... (fingers crossed)


---

Black Panther
aka Dan Richter
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A34 (Linux/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

On 09/27/17, apam said the following...

Yup. If I am online on node 1, and another user, let's just say Andrew l in to the board, he will also be on node 1. If I take a look at nodespy, will bounce between showing one user then the other. It's whenever the o

Oh crap. Did I break your BBS?

No, you didn't. I was just using you as an example... ;)

It seemed that everyone who logged on was put onto node 1, whether someone
else was already logged on or not... I've downgraded to A34 of Mystic, to hopefully eliminate the issue.


---

Black Panther
aka Dan Richter
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A34 (Linux/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

Black Panther said....

It seemed that everyone who logged on was put onto node 1, whether someone else was already logged on or not... I've downgraded to A34 of Mystic, to hopefully eliminate the issue.

Ah ok, so not just me :)

Andrew
--- MagickaBBS v0.7alpha (Linux/x86_64)
* Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)

I'm having these problems, and my system locking up with mystic chewing
up my processor.

Can you provide any information on what the user was doing when this
happened? Where they were last when they logged off etc?

A35 is a *huge* change in the way everything works in Mystic which is why I
was releasing so many of those previews for people to help catch the issues before A35 was officially released.

--- Mystic BBS v1.12 A36 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 09/27/17, Avon said the following...

While lookin at the /mystic/logs directory, I noticed I have over 110 files currently residing there... I have the regular fidopoll.log, node1.log, etc, but I also now have fidopoll[conflicted].log, node1[conflicted].log, node1[conflicted1044].log, etc.

I have not seen/heard of this issue before. No similar things with other OS versions that I am aware of Dan. It sounds like a file permissions thing to me. Something was created but then not correctly deleted or released?

You were right, it was a file locking... I'm really an idiot...

My backup was syncing all files in the /mystic directory as soon as they were changed, and would upload them to the cloud server.

Well, if the log file or the chat1.dat file are locked by the backup
software, then Mystic can't access those files to change them. This would
cause Mystic to create the 'conflicted' files. Also, if the chat1.dat file is locked, Mystic can't determine if anyone is on node 1, so it would put
everyone on node 1...

As I said, I'm an idiot. I was thinking it was a Mystic issue, without
thinking that I had set up the auto-syncing of the backup files... :)

I've had it running for about a week now, with no problems, without the file syncing turned on... So, I have just upgraded back to A35 of Mystic.


---

Black Panther
aka Dan Richter
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

On 10/03/17, Black Panther pondered and said...

You were right, it was a file locking... I'm really an idiot...

No you are not! :)

And that's all I need to say on this matter :)

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 10/03/17, Black Panther said the following...

I've had it running for about a week now, with no problems, without the file syncing turned on... So, I have just upgraded back to A35 of Mystic.

That's good and at least you've found the problem. Hadn't though about filelocking as I use rsync and it doesn't lock them. It just reads them as
they are and should update if needed. I guess that's why some had shutdown
mis and mis2 when backing up.

...If nothing can go wrong, it will - Murphy

--- Mystic BBS v1.12 A35 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

On 10/04/17, bcw142 said the following...

I've had it running for about a week now, with no problems, without t file syncing turned on... So, I have just upgraded back to A35 of Mys

That's good and at least you've found the problem. Hadn't though about filelocking as I use rsync and it doesn't lock them. It just reads them
as they are and should update if needed. I guess that's why some had shutdown mis and mis2 when backing up.

What I'm trying to do, is have it archive the drive, and move it to the
Windows system on the network. I'm just having some issues getting the
Windows system to see the Ubuntu systems, and vice versa. I'm not sure if
Win7 has everything it needs to communicate with Linux...


---

Black Panther
aka Dan Richter
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

On 10/04/17, Black Panther said the following...

What I'm trying to do, is have it archive the drive, and move it to the Windows system on the network. I'm just having some issues getting the Windows system to see the Ubuntu systems, and vice versa. I'm not sure if Win7 has everything it needs to communicate with Linux...

Have you tried filezilla? If your Linux is setup with ssh (sudo apt-get
install ssh filezilla) then you should be able to move files/directories with it. It really uses rsync to do it's work which is built in for most versions
of Linux. When other things fail it's what I use to transfer files. A quick google of filezilla will find Windows versions.

--- Mystic BBS v1.12 A35 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)