Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

show connected users doesn't show them #95

Open
j-boy opened this issue Sep 20, 2012 · 5 comments
Open

show connected users doesn't show them #95

j-boy opened this issue Sep 20, 2012 · 5 comments
Assignees
Labels

Comments

@j-boy
Copy link

j-boy commented Sep 20, 2012

When executing "sudo msm connected" it says that there are no users connected even when there really are:

jexley@scum:~$ sudo msm jonathon connected
[sudo] password for jexley:
No players are connected.
jexley@scum:~$ sudo msm jonathon cmdlog list
Now watching logs (press Ctrl+C to exit):
...
2012-09-20 17:05:23 [INFO] SweetRose112[/<ip address removed>:1567] logged in with entity id 13345 at (371.75971333476247, 63.0, 153.1697803012156)
2012-09-20 17:23:02 [INFO] There are 1/10 players online:
2012-09-20 17:23:02 [INFO] SweetRose112
2012-09-20 17:23:15 [INFO] There are 1/10 players online:
2012-09-20 17:23:15 [INFO] SweetRose112
@Chikuhitsu
Copy link

I have exactly the same problem. At first I suspected something in the timecode comparison (timestamp in the log file / current time) could be involved (I changed my timezone on the day before discovering this). I looked at the script myself, rebooted my system (just to be sure) and it still doesn't work. I'm running the system in UTC.

@ghost ghost assigned marcuswhybrow Sep 29, 2012
@marcuswhybrow
Copy link

I can confirm this problem too. It's most likely a bug in the regex that identifies the log lines it needs to grab.

@TrogloGeek
Copy link
Contributor

I experienced it too, see if patch given in issue #131 corrects your problem (could be caused by the loading of the wrong versionning file)

@eproxus
Copy link

eproxus commented Apr 30, 2014

I still have this problem on version 0.8.16, was this ever fixed?

@kjkazinski
Copy link
Contributor

I applied issue #131's changes but it did not fix the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants