Please wait...
0 files
Subject: Access admin interface from external browser
How can I access the Citadel admin web interface from an external browser? I've tried to open the port used in the firewall, but without luck.
BR,
Stein
Subject: Re: Access admin interface from external browser
2020-03-23 17:23 from SteinTheRuler
Subject: Access admin interface from external browser
How can I access the Citadel admin web interface from an external
browser? I've tried to open the port used in the firewall, but
without luck.
First of all, you have to ensure that Webcit is running. Then you just connect to the ports webcit is using.
Subject: unexpected answer from Citadel server.
Hello,
I've successfully installed citadel, but when i try to connect to the static ip address of my raspberry pi 3, it shows this error message:
Received unexpected answer from Citadel server; bailing out.
Also, when trying to open the citadel-server setup from terminal, the output said that the setup could not connect to a running citadel server: denied acces /var/run/citadel/citadel-admin.socket.
Anyone can help?
Thanks for your patience
The after installing it the installer gives me this output:
The failed ports and sockets are: extensions: TCP port *:504:
(citadel-TCP) ;extensions: TCP port *:143: (IMAP) ;extensions: TCP
Hopefully you are running the Citadel Server as root? It needs root to bind those ports.
Otherwise, binding the ports could be stopped by SElinux or some other security agent.
Subject: cursor still in progress on cdb 02: attempt to write during r/o cursor
Hi Guys, I hope you can help.
I am attempting to migrate an old Citadel server that I have had running on a raspberry pi since 2012.
Now I have successfully followed the EasyInstall process and got an empty server running.
But on exporting the data from the running server, and importing on the new server I get the following :
citserver[7422]: room_ops: CtdlCreateRoom(name=Lobby, type=0, view=0)
citserver[7422]: room_ops: cannot create room <Lobby> - already exists
citserver[7422]: room_ops: CtdlCreateRoom(name=Aide, type=3, view=0)
citserver[7422]: room_ops: cannot create room <Aide> - already exists
citserver[7422]: room_ops: CtdlCreateRoom(name=Local System Configuration, type=3, view=0)
citserver[7422]: room_ops: cannot create room <Local System Configuration> - already exists
citserver[7422]: room_ops: CtdlCreateRoom(name=Trashcan, type=0, view=0)
citserver[7422]: room_ops: cannot create room <Trashcan> - already exists
citserver[7422]: Seeding the pseudo-random number generator...
citserver[7422]: master_startup() finished
citserver[7422]: control: sanity checking the recorded highest message and room numbers
citserver[7422]: control: fixing MMnextroom 13 > 0 , found in 0000000009.Calendar
citserver[7422]: db: cursor still in progress on cdb 02: attempt to write during r/o cursor
citserver[7422]: db: citserver is stopping in order to prevent data loss. uid=0 gid=0 euid=0 egid=0
running undet gdb I get the following backtrace
#0 bailIfCursor (cursors=0x4be704 <masterTSD+4>, msg=0x475b34 "attempt to write during r/o cursor") at database.c:144
#1 0x00411be3 in cdb_store (cdb=13, ckey=0x475eec, ckeylen=10, cdata=0x5bec30, cdatalen=14) at database.c:469
#2 0x00416749 in CtdlSetConfigStr (key=0x475eec "MMnextroom", value=0xbfffc2e0 "13") at config.c:357
#3 0x004167a4 in CtdlSetConfigLong (key=0x475eec "MMnextroom", value=13) at config.c:369
#4 0x00412f03 in control_find_highest (qrbuf=0xbfffc518, data=0x0) at control.c:64
#5 0x00417fa7 in CtdlForEachRoom (CB=0x412e6b <control_find_highest>, in_data=0x0) at room_ops.c:657
#6 0x0041329d in check_control () at control.c:155
#7 0x0040832d in main (argc=2, argv=0xbffff754) at server_main.c:255
So bailIfCursor is going to cdb_abort() if there are any not null cursors. Since CtdlForEachRoom is iterating around a cursor this test will always fail.
but cbd_store only calls bailIfCursor if there is no transaction.
So it seems to me the answer to this issue would be to put a transaction around the loop in CtdlForEachRoom.
This is the first time Ive looked at this code, so I could be making a big mistake, but could anyone who knows the code tell me if I am on the right track.
While investigating i found that setting sanity_diag_mode to 2 (-s2 in the command line)
allows the server to start and the log then contains many lines of the form:
citserver[7426]: control: fixing MMhighest 58110 > 0 , found in Aide
citserver[7426]: control: fixing MMhighest 59355 > 0 , found in Aide
citserver[7426]: control: fixing MMhighest 59648 > 0 , found in Aide
So it looks as though import does not set these high index values.
So I would really like some advice should I
a) just use the -s2 flag and forget about the warnings
b) put in a cdb_begin_transaction /cdb_end_transaction in CtdlForEachRoom
c) Try to work out why ./sendcommand "MIGR import" doesnt set these counts.
Ive limited time since my original raspberry Pi file system is 97% full
Regards
Kim
Subject: Re: cursor still in progress on cdb 02: attempt to write during r/o cursor
Further info :
I put a cdb_begin_transaction() and cdb_end_transaction() around the call to CtdlForEachRoom in check_control, and the server starts!
I decided that changing CtdlForEachRoom may cause problems because it is called from multiple places, unlike check_control which only seems to be called at startup. My intention is to start the migration again from scratch and attempt to document every step.
Rgds Kim