05-23-2002 12:36 PM - edited 03-08-2019 10:44 PM
I installed it, seems to work ok, but if I run cidwebserver -d and let it fork off into the background, it never binds to port 443. If I run it in the FOREGROUND (./cidwebserver) it runs but faults after I login...truss output follows:
getuid() = 0 [0]
getgid() = 1 [100]
open("/usr/nr/etc/routes", O_RDONLY) = 7
fxstat(2, 7, 0xDEF0156C) = 0
lseek(7, 0, SEEK_CUR) = 0
fxstat(2, 7, 0xDEF00C6C) = 0
mmap(0x00000000, 715, PROT_READ, MAP_PRIVATE, 7, 0) = 0xDF5F0000
lseek(7, 715, SEEK_SET) = 715
Incurred fault #6, FLTBOUNDS %pc = 0xDDC01D9D
siginfo: SIGSEGV SEGV_MAPERR addr=0x0000737B
Received signal #11, SIGSEGV [default]
siginfo: SIGSEGV SEGV_MAPERR addr=0x0000737B
*** process killed ***
Ideas?
-brkn!
05-23-2002 01:50 PM
Please reboot the box and then see if using the cidServer script to start and stop the server solves the problem.
05-28-2002 07:26 AM
Worked like a charm. Why I didn't try that the first time will remain a mystery :).
Thanks,
brkn!
05-23-2002 01:56 PM
I've always used the cidServer to stop/start, without issue.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide