Replies: 2 comments
-
Inspecting the database, I see that there are two meshes named the same - and one of them is which my Desktop should be in. I feel as if this is likely to be the cause of the issue, especially as I only see one in the UI. One of those meshes is missing a couple of JSON elements ("creation", "creatorname") ... I've tried to match up the IDs of either of those against that which is listed in the meshagent.msh file on the Desktop, but they appear to be encoded differently (on Desktop, the ID appears to be HEX based, on the server it's far from it...). Any idea how I can match these up? Or am I going down a rabbit hole here??! :O) |
Beta Was this translation helpful? Give feedback.
-
and I've installed a temporary secondary MC2 server ... it won't connect there either!??? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Greetings MC2-ers! I hope that this finds you all well and healthy.
I've been using MC2 for years. Very little issues and even those I've had, have been addressed in a prompt manner. Love this software. I find myself now in an interesting situation where an Ubuntu 22.04.2 Desktop system just refuses to connect to my MC2 server, even though about 40 other systems are working without any issues.
I have a specific group that I wanted this Desktop system to join, and as per usual I select to use the Agent install script for Linux/BSD. This has never failed me before, but I've tried time and time again with this system and it just doesn't pop up in the intended group. I've restarted the services, deleted the /usr/local/mesh_services folder and reinstalled, and this afternoon I eventually tried using the binary download and running it manually (using the direct connect, as opposed to an install) ... nothing.
I'm normally pretty good at hunting down things, but I'm at a bit of a loss to know where to go to even begin to look for on the Desktop itself. The server has some errors logged, but that's to do with a module I've installed, nothing about the basic connectivity of an agent to the server. (The server is using SQLite)
The only thing that I can think of that's different from other systems is that this Desktop is using an SSD rather than a spinning disk ... but I find it hard to believe that that would make THAT much of a difference.
Is there anywhere else I can look to ascertain what's going on with this system?? Any local log files that I can review to see if that gives me some answers? I see that the local meshagent.msh file has the server's name, the MeshServer line looks fine, I'm not sure if I can check the MeshID and/or ServerID is correct.
Update: I've just installed a virtual machine with the same OS as the Desktop itself ... no issues.
Update2: I also created a new mesh group and attempted to add the Desktop into that new group ... same thing, just disappears.
I'm beginning to wonder if the SQLite database is corrupted somehow? Would that make any sense?
Beta Was this translation helpful? Give feedback.
All reactions