Thanks!
I'm going to restore a snapshot of my VM so I can try again; when I try
to log in with http; and the "citadel" process just crashes.
webcit[2802]: POST /ajax_login_username_password HTTP/1.1
citserver[2801]: [(not logged in)(0)] USER ***
citserver[2801]: user_ops: cmd_user(***)
citserver[2801]: user_ops: CtdlLoginExistingUser(***)
citserver[2801]: [***(11)] <password command hidden from log>
citserver[2801]: user_ops: <***> logged in
*** buffer overflow detected ***: citserver terminated
pid=2801 exited, status=6
ctdlvisor: citserver exited normally - ending AppImage session
webcit[2802]: StrBuf_ServGetln(): Server connection broken: Resource
temporarily unavailable
webcit[2802]: HTTP: 200 [0.003725] POST /ajax_login_username_password
...# webcit[2802]: POST /ajax_login_username_password HTTP/1.1
webcit[2802]: Can't connect [/usr/local/citadel/citadel.socket]:
Connection refused
webcit[2802]: HTTP: 200 [0.001161] POST /ajax_login_username_password
(refreshing the browser)
webcit[2802]: GET /push?url=do_welcome HTTP/1.1
webcit[2802]: Can't connect [/usr/local/citadel/citadel.socket]:
Connection refused
webcit[2802]: HTTP: 200 [0.000999] GET /push?url=do_welcome
But the backup can only be done during the night when there is no staff
using it.
On 1/24/21 5:19 PM, IGnatius T Foobar wrote:
Just use HTTP for now. I will work out the certificate stuff as part
of the installation process. Again, right now I just want to know
that it runs on your system. Yesterday I figured out why it was
corrupting the database: when you pressed Ctrl-C it somehow got two
copies of citserver running at the same time and writing to the same
database files. This has been fixed.
The new downloads:
https://easyinstall.citadel.org/Citadel-x86_64.AppImage
<https://easyinstall.citadel.org/Citadel-x86_64.AppImage> (64-bit x86)
https://easyinstall.citadel.org/Citadel-armhf.AppImage
<https://easyinstall.citadel.org/Citadel-armhf.AppImage> (32-bit ARM)
I will be busy with other things this week, so hopefully these are
stable enough for you guys to give them a really good workup. Again,
they are NOT ready for production. Also now you need to add the word
"run" to the command line, to tell it to run Citadel services. The
other commands don't work yet.
Once we have the base system working, we will add the following
installation features:
* Citadel Server and WebCit will share an SSL key and certificate.
Perhaps we can even figure out how to change it while running.
* Automatic installation of systemd unit files.
* Automatic upgrade.
* Built-in commands to generate both portable (binary) and
non-portable (XML) backups.
