Closed PixelHeroMedia closed 7 years ago
First we have to resolve the very first problem: sphere can not found spheretables.scp. You really have scripts/spheretables.scp?
It does find it. It is reading the script names in spheretables and trying to load them just after it says it cant open it. All files are 100% there in the right place. It seems to say it cannot open it, but it can. Its outputting all the info from inside these files, just never seems to load them into sphere or something?
Why does it think its a 'dir' and not a file? Thats whats confusing me also.
Are you running sphere as root?
Maybe at line 583 you have a template which has those items? Also, have you tried latest nightly? Have you noticed since which commit this issue occurs?
Those templates do reference them, but not sure what you're getting at as they're basic defs which exist in previously loaded files, and that's just a small example of the 1000s of missing defs.
Nothing custom at all, litrelly downloaded and run as basic as it gets.
Running as root yes. Same errors as with a user.
Can someone else spin up centos7 and try?
I don't know when it started this is the first 56c build I'm trying, latest nightly has same errors.
I can attach the full log if you think it'll help On 26 May 2016 18:43, "cbnolok" notifications@github.com wrote:
Maybe at line 583 you have a template which has those items? Also, have you tried latest nightly? Have you noticed since which commit this issue occurs?
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/Sphereserver/Source/issues/64#issuecomment-221942689
More info:
Looking for the errors its from CFileList calling stat on the script files. I ran this on the server from the same directory as spheresvr and they work fine
File: ‘scripts/sphere_serv_triggers.scp’
Size: 5571 Blocks: 16 IO Block: 4096 regular file
Device: 802h/2050d Inode: 4303576983 Links: 1
Access: (0600/-rw-------) Uid: ( 0/ root) Gid: ( 0/ root)
Context: unconfined_u:object_r:default_t:s0
Access: 2016-05-27 13:10:32.793806202 +0100
Modify: 2016-05-25 12:33:44.159164219 +0100
Change: 2016-05-25 12:34:18.781092621 +0100
Birth: -```
Maybe something weird with what sphere is thinking the base directory is? I am not that experienced in c++ and can't find anything where sphere is deciding what directory its in, anyone know what logic it uses to determine this?
spheretables.scp uses / for a folder. However linux needs a \
But didnt seem to help
Probably using \ would work for both windows and linux, i may give it a look at this next week
Nope, check sphere.ini for there specified base path. Seems you left it empty. And backslash () does not work on Linux as a separator. Only normal slashes (/) are allowed. And there are supported on all OSes.
On Fri, May 27, 2016, 21:10 cbnolok notifications@github.com wrote:
Probably using \ would work for both windows and linux, i may give it a look at this next week
— You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/Sphereserver/Source/issues/64#issuecomment-222216048, or mute the thread https://github.com/notifications/unsubscribe/ALUUB49po2iCTr9HaFito26jSXd6BWI-ks5qFzOmgaJpZM4Indor .
I haven't understood if you have solved by changing the slash, and to which one Il 27 mag 2016 17:01, "Richard Edwards" notifications@github.com ha scritto:
OMG, figured it out.
spheretables.scp uses / for a folder. However linux needs a \
Might be worth building a linux one for people to use?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Sphereserver/Source/issues/64#issuecomment-222169936, or mute the thread https://github.com/notifications/unsubscribe/AOWhJOsaPDpNr69t-fu-UgL4dihfn8I_ks5qFwdngaJpZM4Indor .
So where to look next? I don't get why stat is failing On 27 May 2016 22:33, "cbnolok" notifications@github.com wrote:
I haven't understood if you have solved by changing the slash, and to which one Il 27 mag 2016 17:01, "Richard Edwards" notifications@github.com ha scritto:
OMG, figured it out.
spheretables.scp uses / for a folder. However linux needs a \
Might be worth building a linux one for people to use?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub <https://github.com/Sphereserver/Source/issues/64#issuecomment-222169936 , or mute the thread < https://github.com/notifications/unsubscribe/AOWhJOsaPDpNr69t-fu-UgL4dihfn8I_ks5qFwdngaJpZM4Indor
.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Sphereserver/Source/issues/64#issuecomment-222258008, or mute the thread https://github.com/notifications/unsubscribe/AKMdkCL8sjRAoEFdaf3U3_1cgAmvSDkYks5qF2MggaJpZM4Indor .
I would try to chown -R /sphere youruser && chmod -R u+rw /sphere Then su to that user and try to start sphere by him.
Already done, I have tried the same with root and a user called sphere, same errors On 27 May 2016 22:39, "Vjacheslav Kanivetc" notifications@github.com wrote:
I would try to chown -R /sphere youruser && chmod -R u+rw /sphere Then su to that user and try to start sphere by him.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Sphereserver/Source/issues/64#issuecomment-222259154, or mute the thread https://github.com/notifications/unsubscribe/AKMdkDrlOBt9V_efTfyynzaLOXWco2D6ks5qF2SHgaJpZM4Indor .
Any other ideas? Anyone else been able to test this?
I tested and worked for me, but not on Centos (i think is not related to the OS). The only way we can test your env is sending us your full sphere i think...
I have nothing but Pre-release 56c for Linux, Pre-release 56c Scripts.
I just got the latest nightly too and same issues.
Here is exactly how I set up:
Nothing more to it.
Oh, all chown as root, and also tried chown as a user, same issues regardless.
Check paths, linux is case sensitive as well. also try with a full path for scripts ie /home/bob/sphere/scripts I vaguely remember hitting similar issues when trying to run on linux.
last month I tested an CentOS 7 server and also got these problems when I compiled spheresvr myself. The problem is: the compiler was building sphere in 64bit and this was making sphere return tons of console errors because sphere is not 64bit. To fix it, I just compiled in 32bit where I'm been able to boot the server running perfectly without a single error
I already updated source files to build in 32bit by default and also added some CentOS 7 package instructions here on github page, so if you still having these problems, just update your source files and install these CentOS 7 packages
In the pre-release build, on Centos7 I am getting these errors when Sphere starts. All permissions and structure are correct.
The below error happens for every file as it loads. It claims it cannot open 'input dir' but the user running sphere has required access (tested with root + custom user).
As you can see it seems to read the file, but then references seem to not ever exist, so everything fails. After loading sphere continues to pretend its up and running.
I have tried with a clean sphere.ini and custom, it does not change the issue. I have tried with the latest Nightly as well as the Debug version and nothing works any different.
Upon typing 'x' to quit I get the following:
Resync simply throws all the startup errors again. Whats more confusing is that these 'symbols' do not exist in the mentioned file AT ALL.
So where on earth is it getting that from?!