Language:
switch to room list switch to menu My folders
Go to page: First ... 19 20 21 22 [23] 24 25 26 27 ... Last
[#] Sun Nov 29 2020 07:00:26 EST from SquareRootSquared

Subject: Webcit Freeze Requiring Process Kill/Restart

[Reply] [ReplyQuoted] [Headers] [Print]

Running Citadel 929 using the recommended easy install method. Setting Lobby to use a file directory, then uploading a file, then trying to delete the file.. causes webcit to emit an error and sometimes freeze requiring a kill/restart of the webcit process. Web browser used is Google Chrome and accessing webcit via http://.



[#] Sun Nov 29 2020 10:38:02 EST from ParanoidDelusions

[Reply] [ReplyQuoted] [Headers] [Print]

Sometimes I'm too verbose. My question is: 

For an upgrade, do I need to download and install from the latest source, compiling with "make upgrade"? Or can I run the Easy-Install over the top of my currently running installation of Citadel?

I suppose this may seem obvious, implied from the instructions - but I need it spelled out, I guess. 



[#] Sun Nov 29 2020 10:53:47 EST from ParanoidDelusions

[Reply] [ReplyQuoted] [Headers] [Print]

One additional question. In either case, does the source Citadel need to be on the same version as the target Citadel? 

Because upgrading the source Citadel to the latest version is the major hurdle for me, right now. 

 

Thu Nov 26 2020 15:52:16 EST from omatnet @ Uncensored

Here is another option for you, using the "MIGR" parameter of sendcommand:

On the Pi3B do:

sudo /usr/local/citadel/sendcommand -w900 "MIGR export" > ~/CitBackup.xml

Then transfer the xml file to the i5 and there do

sudo /usr/local/citadel/sendcommand -w900 "MIGR import" < ~/CitBackup.xml

The reason for the -w900 is to give the operation enough time (900 seconds = 15 min) to complete, otherwise sendcommand will terminate with its 60s timeout default.

 

If you use ctdlmigrate - it works well, just remember that on the Pi3B you need to allow SSH connection and to permit SSH root user incoming connection. So make sure that a remote root login password is set using 'sudo passwd' (to allow remote root SSH connection you edit /etc/ssh/sshd_config  and make sure that the parameter "PermitRootLogin" is set to "yes"). When done, for security and safety, restore sshd_config to the way it was.

 

 

Wed Nov 25 2020 08:17:37 EST from ParanoidDelusions @ Uncensored

Any one have ideas on how to migrate Citadel from a Pi 3B running Raspbian to an i5 running Debian? 




 



 



[#] Sun Nov 29 2020 10:56:33 EST from ParanoidDelusions

Subject: Re: Corrupted attachments

[Reply] [ReplyQuoted] [Headers] [Print]

 

Tue Nov 24 2020 07:44:55 EST from ParanoidDelusions @ Uncensored Subject: Re: Corrupted attachments

 

Tue Nov 24 2020 02:03:58 ESTfrom jtbreazeoutlook.com @ Uncensored Subject: Re: Corrupted attachments

Great, thanks for the quick reply. I'm liking Ubuntu for the server OS, with the more current repositories, so I'll definitely be staying away from OpenSuse. I'll be keeping an eye on future updates, so I can switch back to the pi, though, it was working great otherwise, there aren't enough users with enough demand to overtax the 4 B, I was sitting at just over 1gb of ram use, and 10% cpu. I'm sold on Citadel, for sure.

 

I mean, ideally we would figure out what the problem is on the Pi - but - building an Intel system might be the best first step. If it happens *there*, it seems to be some kind of operator error. If it doesn't... it is on the Pi architecture or Distro. 

 

By the way, I built out a Citadel on an i86 box, and tested by downloading an image and uploading it as an attachment. 

No square box, no file corruption - you click on the image, and it opens up in a new tab. 

So, this seems like something specific to Pi - possibly to Raspbian. 

 



[#] Sun Nov 29 2020 12:05:42 EST from warbaby

Subject: Re: STARTTLS

[Reply] [ReplyQuoted] [Headers] [Print]

TLS doesn't run on port 25.

In Webcit, see Administration.. Edit site-wide configuration.. SMTP tab..

Encryption is on port 465/587

Fri Nov 27 2020 04:55:41 PM EST from guesty2k @ Uncensored Subject: Re: STARTTLS

Does anyone know how to resolve this? 

when connecting to port 25, it does not advertise 250-STARTTLS

 

 



 



[#] Sun Nov 29 2020 12:18:43 EST from warbaby

Subject: Does Migration src and dest need to be the same Citadel version?

[Reply] [ReplyQuoted] [Headers] [Print]

[Not to be rude or anything, but whoever is writing these posts with no Subject line.. if you want free help, please care enough about the community to write descriptive Subject lines.]

YES, in most cases it absolutely does need to be the same version, otherwise you are wasting your time.

If you can do an upgrade in place with easyinstall (which would be the best case, if your original installation was done with easyinstall )

First, backup your database!

service citadel stop # or, however you stop citadel

cp /usr/local/citadel/data/* /someplace

THEN, if and only if your "source" installation was installed with easyinstall, you can run easy install again.

[You might want to grab my -k --keep source version of easyinstall, which is a few messages back. It will retain a copy of all the sources in /usr/src for you, with a configured build environment in case you want to build/upgrade again.. ]

After both systems are on the same version, you can use the migration method which has been suggested.

If you CAN'T upgrade, or can't do the migration for whatever reason:

[Check the posts here for various mentions of the "Slacker Method" of migration. It has been discussed recently.]

Essentially, you can setup a client [such as Thunderbird] with access to both systems, then drag your messages into place through the client. 

It's a good time to cleanup and decruft mailboxes anyway, so don't feel like it's really a bad thing.

 

 

Sun Nov 29 2020 10:53:47 AM EST from ParanoidDelusions @ Uncensored

One additional question. In either case, does the source Citadel need to be on the same version as the target Citadel? 

Because upgrading the source Citadel to the latest version is the major hurdle for me, right now. 

 

Thu Nov 26 2020 15:52:16 EST from omatnet @ Uncensored

Here is another option for you, using the "MIGR" parameter of sendcommand:

On the Pi3B do:

sudo /usr/local/citadel/sendcommand -w900 "MIGR export" > ~/CitBackup.xml

Then transfer the xml file to the i5 and there do

sudo /usr/local/citadel/sendcommand -w900 "MIGR import" < ~/CitBackup.xml

The reason for the -w900 is to give the operation enough time (900 seconds = 15 min) to complete, otherwise sendcommand will terminate with its 60s timeout default.

 

If you use ctdlmigrate - it works well, just remember that on the Pi3B you need to allow SSH connection and to permit SSH root user incoming connection. So make sure that a remote root login password is set using 'sudo passwd' (to allow remote root SSH connection you edit /etc/ssh/sshd_config  and make sure that the parameter "PermitRootLogin" is set to "yes"). When done, for security and safety, restore sshd_config to the way it was.

 

 

Wed Nov 25 2020 08:17:37 EST from ParanoidDelusions @ Uncensored

Any one have ideas on how to migrate Citadel from a Pi 3B running Raspbian to an i5 running Debian? 




 



 



 



[#] Sun Nov 29 2020 12:29:21 EST from warbaby

Subject: Re: Webcit Freeze Requiring Process Kill/Restart

[Reply] [ReplyQuoted] [Headers] [Print]

You might start by turning on the debugging log, so you can see what's going on.

First stop/kill all your citserver processes.. 

Have a look at /etc/systemd/system/citadel.server OR /etc/init.d/citadel [Wherever your init scripts are..]

Launch citserver with a new log level, something like

/usr/local/citadel/citserver -x 7

(7 is log level 'debug')

See these docs:

Cit Server https://www.citadel.org/citserver.html

Log level [in the system administration manual] https://www.citadel.org/system_administration_manual.html

 

 

Sun Nov 29 2020 07:00:26 AM EST from SquareRootSquared @ Uncensored Subject: Webcit Freeze Requiring Process Kill/Restart

Running Citadel 929 using the recommended easy install method. Setting Lobby to use a file directory, then uploading a file, then trying to delete the file.. causes webcit to emit an error and sometimes freeze requiring a kill/restart of the webcit process. Web browser used is Google Chrome and accessing webcit via http://.



 



[#] Sun Nov 29 2020 12:33:33 EST from warbaby

Subject: Re: Chat/Instant Messenger send/receive Delay

[Reply] [ReplyQuoted] [Headers] [Print]

Funny you should mention this.. One of my tasks today is to replace the js chat popup with ConverseJs..

* This is not official*, however it is an attempt to address a security issues raised by the existing popup code. 

I have nothing to say about your delay issue at the moment, but I'll certainly take a look at it.

*Meaning, not an official Citadel Project thing.  It's just an experiment.

Sat Nov 28 2020 12:15:09 PM EST from SquareRootSquared @ Uncensored Subject: Chat/Instant Messenger send/receive Delay

I am measuring a 1 to 8 second delay between when a line of text is sent and when it is displayed on the client side instant messenger or similarly on the room's chat viewer screen. Is this delay normal operation and is there any way to decrease this delay?



 



[#] Sun Nov 29 2020 12:48:38 EST from warbaby

Subject: running easyinstall by piping standard input directly to bash as root

[Reply] [ReplyQuoted] [Headers] [Print]

[Fyi, if you're still installing, I encourage you to use the -keep src version of easyinstall, posted here not long ago. It's current, and will help you be able to poke around and learn.]

My personal security regime is to download any/all scripts first, then take a look at them and see what they do, before setting anything to be executable..

LEAST OF ALL, running them as root.

But, because everybody wants a "one line installer", you'll often see "piping standard input to bash"  [I realize the online documentation shows this..]

But, SERIOUSLY, all it takes is one time to be bitten & burned!

What if someone as a joke, or for evil, commits "#!/bin/bash echo " installing.. "; rm -rf /" to some script out there?

You run that root, and it's FAREWELL to your carefully configured system.

Developing the habitual behavior of "download and examine first" will spare you that upset.

 

Sat Nov 28 2020 10:01:23 PM EST from ParanoidDelusions @ Uncensored

As noted elsewhere, I'm an idiot. You have to execute "bash install" after clicking the easy-install link on citadel org, as root or sudo, in order to actually run the bash script that installs Citadel. 

Onward to the next challenge for the Linux impaired... 


Sat Nov 28 2020 14:11:29 EST from ParanoidDelusions @ Uncensored

The Easy-Install doesn't seem to work with Raspbian or Debian at this point...

 

I vaguely recall issues like this the first time, and that it was mostly me not understanding the shell scripts that the Easy Install runs. 

 



 



 



[#] Sun Nov 29 2020 12:49:56 EST from ParanoidDelusions

Subject: Hello, I'm "Whoever" - was Re: Does Migration src and dest need...

[Reply] [ReplyQuoted] [Headers] [Print]

I'm an old school Z80 Citadel user and sysop - so I just tend to have a blind spot to some of the more modern features of Webcit, like subject lines. I don't really think of it as groupware or a modern message forum. Sorry about that. Kind of like hitting <E>nter instead of <R>eply. It has nothing to do with not caring about the community - it has to do with being an old dog. But I appreciate the free help. I'll try to keep this advice in mind for future requests for help in this room. Thanks. Crusty  old codgers offering free help to clueless noobs IS a Citadel tradition though - so at least that part isn't my first rodeo, and makes me feel right at home.. ;)

So, I've actually just taken the whole SD from my "production" Pi and made an image of it, wrote that image to another card, and I'm working on a second Pi to do the upgrade and migration. I might lose a few messages - but it gives me a test environment I can FU and rebuild very quickly and leaves the Citadel up and running untouched.

I had decided to just download the source tars, extract them and configure, make and make upgrade them. ./configure seems to run fine, but make doesn't really do anything and make install throws up an error. Not sure what I am doing wrong.

But maybe you've given me some hints as to what is going wrong here - and certainly you've provided more clarity on what the options are, and where to find the info I'll need to get this all resolved.

Thanks.


Sun Nov 29 2020 12:18:43 EST from warbaby @ Uncensored Subject: Does Migration src and dest need to be the same Citadel version?

[Not to be rude or anything, but whoever is writing these posts with no Subject line.. if you want free help, please care enough about the community to write descriptive Subject lines.]

YES, in most cases it absolutely does need to be the same version, otherwise you are wasting your time.

If you can do an upgrade in place with easyinstall (which would be the best case, if your original installation was done with easyinstall )

First, backup your database!

service citadel stop # or, however you stop citadel

cp /usr/local/citadel/data/* /someplace

THEN, if and only if your "source" installation was installed with easyinstall, you can run easy install again.

[You might want to grab my -k --keep source version of easyinstall, which is a few messages back. It will retain a copy of all the sources in /usr/src for you, with a configured build environment in case you want to build/upgrade again.. ]

After both systems are on the same version, you can use the migration method which has been suggested.

If you CAN'T upgrade, or can't do the migration for whatever reason:

[Check the posts here for various mentions of the "Slacker Method" of migration. It has been discussed recently.]

Essentially, you can setup a client [such as Thunderbird] with access to both systems, then drag your messages into place through the client. 

It's a good time to cleanup and decruft mailboxes anyway, so don't feel like it's really a bad thing.

 

 

Sun Nov 29 2020 10:53:47 AM EST from ParanoidDelusions @ Uncensored

One additional question. In either case, does the source Citadel need to be on the same version as the target Citadel? 

Because upgrading the source Citadel to the latest version is the major hurdle for me, right now. 

 

Thu Nov 26 2020 15:52:16 EST from omatnet @ Uncensored

Here is another option for you, using the "MIGR" parameter of sendcommand:

On the Pi3B do:

sudo /usr/local/citadel/sendcommand -w900 "MIGR export" > ~/CitBackup.xml

Then transfer the xml file to the i5 and there do

sudo /usr/local/citadel/sendcommand -w900 "MIGR import" < ~/CitBackup.xml

The reason for the -w900 is to give the operation enough time (900 seconds = 15 min) to complete, otherwise sendcommand will terminate with its 60s timeout default.

 

If you use ctdlmigrate - it works well, just remember that on the Pi3B you need to allow SSH connection and to permit SSH root user incoming connection. So make sure that a remote root login password is set using 'sudo passwd' (to allow remote root SSH connection you edit /etc/ssh/sshd_config  and make sure that the parameter "PermitRootLogin" is set to "yes"). When done, for security and safety, restore sshd_config to the way it was.

 

 

Wed Nov 25 2020 08:17:37 EST from ParanoidDelusions @ Uncensored

Any one have ideas on how to migrate Citadel from a Pi 3B running Raspbian to an i5 running Debian? 




 



 



 



 



[#] Sun Nov 29 2020 13:08:54 EST from ParanoidDelusions

Subject: Re: Hello, I'm "Whoever" - was Re: Does Migration src and dest need...

[Reply] [ReplyQuoted] [Headers] [Print]

That did the trick, Warbaby. Thanks for the help - and really, I promise to use the subject line going forward when I request help. I just didn't know it was customary here. 

 

 


[#] Mon Nov 30 2020 00:41:58 EST from SquareRootSquared

Subject: Re: Webcit Freeze Requiring Process Kill/Restart

[Reply] [ReplyQuoted] [Headers] [Print]

 

Sun Nov 29 2020 12:29:21 EST from warbaby @ Uncensored Subject: Re: Webcit Freeze Requiring Process Kill/Restart

You might start by turning on the debugging log, so you can see what's going on.

First stop/kill all your citserver processes.. 

Have a look at /etc/systemd/system/citadel.server OR /etc/init.d/citadel [Wherever your init scripts are..]

Launch citserver with a new log level, something like

/usr/local/citadel/citserver -x 7

(7 is log level 'debug')

See these docs:

Cit Server https://www.citadel.org/citserver.html

Log level [in the system administration manual] https://www.citadel.org/system_administration_manual.html

 

 

Sun Nov 29 2020 07:00:26 AM EST from SquareRootSquared @ Uncensored Subject: Webcit Freeze Requiring Process Kill/Restart

Running Citadel 929 using the recommended easy install method. Setting Lobby to use a file directory, then uploading a file, then trying to delete the file.. causes webcit to emit an error and sometimes freeze requiring a kill/restart of the webcit process. Web browser used is Google Chrome and accessing webcit via http://.



 



 

Done.

Here is the journalctl log snippet (had just tried to delete a picture file named "under the harvest moon.jpg" from the Lobby):

Nov 29 22:59:18 fgnet1.accesslab.com webcit[1026]: webcit[1026]: HTTP: 200 [0.000793] GET /chat_rwho

Nov 29 22:59:18 fgnet1.accesslab.com webcit[1026]: #[0;2;37m#[0;1;31m#[0;2;37mGET /chat_rwho HTTP/1.1#[0m

Nov 29 22:59:18 fgnet1.accesslab.com webcit[1026]: HTTP: 200 [0.000793] GET /chat_rwho

Nov 29 22:59:18 fgnet1.accesslab.com webcit[1026]: webcit[1026]: GET /chat_recv HTTP/1.1

Nov 29 22:59:18 fgnet1.accesslab.com webcit[1026]: webcit[1026]: HTTP: 200 [0.000803] GET /chat_recv

Nov 29 22:59:18 fgnet1.accesslab.com webcit[1026]: #[0;2;37m#[0;1;31m#[0;2;37mGET /chat_recv HTTP/1.1#[0m

Nov 29 22:59:18 fgnet1.accesslab.com webcit[1026]: HTTP: 200 [0.000803] GET /chat_recv

Nov 29 22:59:20 fgnet1.accesslab.com webcit[1026]: webcit[1026]: GET /chat_recv HTTP/1.1

Nov 29 22:59:20 fgnet1.accesslab.com webcit[1026]: webcit[1026]: HTTP: 200 [0.000781] GET /chat_recv

Nov 29 22:59:20 fgnet1.accesslab.com webcit[1026]: #[0;2;37m#[0;1;31m#[0;2;37mGET /chat_recv HTTP/1.1#[0m

Nov 29 22:59:20 fgnet1.accesslab.com webcit[1026]: HTTP: 200 [0.000781] GET /chat_recv

Nov 29 22:59:20 fgnet1.accesslab.com webcit[1026]: webcit[1026]: GET /delete_file?file=Under%2Dthe%2DHarvest%2DMoon%2D16.jpg HTTP/1.1

Nov 29 22:59:20 fgnet1.accesslab.com kernel: webcit[1026]: segfault at a84a0880 ip 00007ff2de308cb4 sp 00007ffca84a06d8 error 6 in libcitadel.so.4.0.925[7ff2de302000+15000]

Nov 29 22:59:20 fgnet1.accesslab.com kernel: Code: 00 00 00 48 83 c4 08 5b 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 90 48 85 ff 74 1b 48 8b 17 48 85 d2 74 13 8b 47 18 85 c0 75 0c <c6> 02 00 48 c7 47 10 00 00 00 00 c3 b8 ff ff ff ff c3 66 2e 0f 1f

Nov 29 22:59:20 fgnet1.accesslab.com citserver[375]: citserver[375]: Citadel client disconnected: ending session.

Nov 29 22:59:20 fgnet1.accesslab.com citserver[375]: citserver[375]: context: [ 12]SRV[citadel-UDS] Session ended.

Nov 29 22:59:20 fgnet1.accesslab.com citserver[375]: citserver[375]: Citadel client disconnected: ending session.

Nov 29 22:59:20 fgnet1.accesslab.com citserver[375]: citserver[375]: context: [ 11]SRV[citadel-UDS] Session ended.

Nov 29 22:59:20 fgnet1.accesslab.com webcit[1026]: #[0;2;37m#[0;1;31m#[0;2;37mGET /delete_file?file=Under%2Dthe%2DHarvest%2DMoon%2D16.jpg HTTP/1.1#[0m

Nov 29 22:59:20 fgnet1.accesslab.com systemd[1]: #[0;1;39m#[0;1;31m#[0;1;39mwebcit-http.service: Main process exited, code=killed, status=11/SEGV#[0m

Nov 29 22:59:20 fgnet1.accesslab.com citserver[375]: Citadel client disconnected: ending session.

Nov 29 22:59:20 fgnet1.accesslab.com systemd[1]: #[0;1;39m#[0;1;31m#[0;1;39mwebcit-http.service: Failed with result 'signal'.#[0m

Nov 29 22:59:20 fgnet1.accesslab.com citserver[375]: context: [ 12]SRV[citadel-UDS] Session ended.

Nov 29 22:59:20 fgnet1.accesslab.com citserver[375]: Citadel client disconnected: ending session.

Nov 29 22:59:20 fgnet1.accesslab.com citserver[375]: context: [ 11]SRV[citadel-UDS] Session ended.

Nov 29 22:59:24 fgnet1.accesslab.com systemd[1]: webcit-http.service: Service RestartSec=3s expired, scheduling restart.

Nov 29 22:59:24 fgnet1.accesslab.com systemd[1]: webcit-http.service: Scheduled restart job, restart counter is at 1.

Nov 29 22:59:24 fgnet1.accesslab.com systemd[1]: Stopped Citadel web service.

Nov 29 22:59:24 fgnet1.accesslab.com systemd[1]: Started Citadel web service.

Nov 29 22:59:24 fgnet1.accesslab.com webcit[1054]: webcit[1054]: Changing directory to /usr/local/webcit/

Nov 29 22:59:24 fgnet1.accesslab.com webcit[1054]: Changing directory to /usr/local/webcit/

Nov 29 22:59:24 fgnet1.accesslab.com webcit[1054]: webcit[1054]: WebCit 926

Nov 29 22:59:24 fgnet1.accesslab.com webcit[1054]: #[0;1;39m#[0;1;31m#[0;1;39mWebCit 926#[0m

Nov 29 22:59:24 fgnet1.accesslab.com webcit[1054]: webcit[1054]: Copyright (C) 1996-2020 by the citadel.org team

Nov 29 22:59:24 fgnet1.accesslab.com webcit[1054]: #[0;1;39m#[0;1;31m#[0;1;39mCopyright (C) 1996-2020 by the citadel.org team#[0m

Nov 29 22:59:24 fgnet1.accesslab.com webcit[1054]: webcit[1054]:

Nov 29 22:59:24 fgnet1.accesslab.com webcit[1054]:

Nov 29 22:59:24 fgnet1.accesslab.com webcit[1054]: webcit[1054]: This program is open source software: you can redistribute it and/or

Nov 29 22:59:24 fgnet1.accesslab.com webcit[1054]: #[0;1;39m#[0;1;31m#[0;1;39mThis program is open source software: you can redistribute it and/or#[0m

Nov 29 22:59:24 fgnet1.accesslab.com webcit[1054]: webcit[1054]: modify it under the terms of the GNU General Public License, version 3.


Here is a snippet from syslog during the same time frame:

Nov 29 22:54:15 fgnet1 kernel: [60156.918691] webcit[857]: segfault at 18a85cc0 ip 00007fc21c0f8cb4 sp 00007fc218a85b18 error 6 in libcitadel.so.4.0.925[7fc21c0f2000+15000]

Nov 29 22:54:15 fgnet1 kernel: [60156.918722] Code: 00 00 00 48 83 c4 08 5b 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 90 48 85 ff 74 1b 48 8b 17 48 85 d2 74 13 8b 47 18 85 c0 75 0c <c6> 02 00 48 c7 47 10 00 00 00 00 c3 b8 ff ff ff ff c3 66 2e 0f 1f

Nov 29 22:59:20 fgnet1 kernel: [60461.992543] webcit[1026]: segfault at a84a0880 ip 00007ff2de308cb4 sp 00007ffca84a06d8 error 6 in libcitadel.so.4.0.925[7ff2de302000+15000]

Nov 29 22:59:20 fgnet1 kernel: [60461.992555] Code: 00 00 00 48 83 c4 08 5b 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 90 48 85 ff 74 1b 48 8b 17 48 85 d2 74 13 8b 47 18 85 c0 75 0c <c6> 02 00 48 c7 47 10 00 00 00 00 c3 b8 ff ff ff ff c3 66 2e 0f 1f

Nov 29 22:59:26 fgnet1 kernel: [60467.622064] webcit[1054]: segfault at b0 ip 0000556dc01c1a76 sp 00007ffc2e641610 error 4 in webcit[556dc01bf000+66000]

Nov 29 22:59:26 fgnet1 kernel: [60467.622076] Code: 00 00 e8 cd e9 ff ff 48 8b 45 e8 48 89 45 e0 e9 91 00 00 00 48 8b 45 d0 8b 80 90 00 00 00 85 c0 0f 84 82 00 00 00 48 8b 45 e8 <8b> 50 30 48 8b 45 d0 8b 80 90 00 00 00 39 c2 75 6d 8b 05 b3 6d 09

I also will try and upload a few pics showing visual effects, please see the upload directory for this room..

 



[#] Mon Nov 30 2020 00:54:32 EST from SquareRootSquared

Subject: Re: Chat/Instant Messenger send/receive Delay

[Reply] [ReplyQuoted] [Headers] [Print]

 

Sun Nov 29 2020 12:33:33 EST from warbaby @ Uncensored Subject: Re: Chat/Instant Messenger send/receive Delay

Funny you should mention this.. One of my tasks today is to replace the js chat popup with ConverseJs..

* This is not official*, however it is an attempt to address a security issues raised by the existing popup code. 

I have nothing to say about your delay issue at the moment, but I'll certainly take a look at it.

*Meaning, not an official Citadel Project thing.  It's just an experiment.

Sat Nov 28 2020 12:15:09 PM EST from SquareRootSquared @ Uncensored Subject: Chat/Instant Messenger send/receive Delay

I am measuring a 1 to 8 second delay between when a line of text is sent and when it is displayed on the client side instant messenger or similarly on the room's chat viewer screen. Is this delay normal operation and is there any way to decrease this delay?



 



 

On my test bench I have both the sending station and the receiving station in front of me and can watch in realtime how long it takes after I press the enter key on a line of text to show up on the receiving end. I would expect the line of text to display at the receiver almost instantly since both boxes and the server box are plugged into the same lan switch. However, I am seeing lots of delay of up to 8 seconds, with the average delay of around 4 seconds. This amount of delay can make an average chat conversation that normally would take 10 minutes end up taking 30 minutes for the same conversation which could be quite annoying during certain types of conversations. What is causing this strange variable delay in line transmissions? Can it be adjusted/tweaked?

 



[#] Mon Nov 30 2020 10:25:10 EST from warbaby

Subject: Re: Hello, I'm "Whoever" - was Re: Does Migration src and dest need...

[Reply] [ReplyQuoted] [Headers] [Print]

No worries, no need for explanations.. I'm just hoping to improve our documentation.

If you used the -k (keep source) version of easyinstall.. and your source is in somthing like

/usr/src/citadel-build-xxx

and then you make some changes..

you want to run

make upgrade

instead of just make.

then

make install

 

Sun Nov 29 2020 12:49:56 PM EST from ParanoidDelusions @ Uncensored Subject: Hello, I'm "Whoever" - was Re: Does Migration src and dest need...

I'm an old school Z80 Citadel user and sysop - so I just tend to have a blind spot to some of the more modern features of Webcit, like subject lines. I don't really think of it as groupware or a modern message forum. Sorry about that. Kind of like hitting <E>nter instead of <R>eply. It has nothing to do with not caring about the community - it has to do with being an old dog. But I appreciate the free help. I'll try to keep this advice in mind for future requests for help in this room. Thanks. Crusty  old codgers offering free help to clueless noobs IS a Citadel tradition though - so at least that part isn't my first rodeo, and makes me feel right at home.. ;)

So, I've actually just taken the whole SD from my "production" Pi and made an image of it, wrote that image to another card, and I'm working on a second Pi to do the upgrade and migration. I might lose a few messages - but it gives me a test environment I can FU and rebuild very quickly and leaves the Citadel up and running untouched.

I had decided to just download the source tars, extract them and configure, make and make upgrade them. ./configure seems to run fine, but make doesn't really do anything and make install throws up an error. Not sure what I am doing wrong.

But maybe you've given me some hints as to what is going wrong here - and certainly you've provided more clarity on what the options are, and where to find the info I'll need to get this all resolved.

Thanks.


Sun Nov 29 2020 12:18:43 EST from warbaby @ Uncensored Subject: Does Migration src and dest need to be the same Citadel version?

[Not to be rude or anything, but whoever is writing these posts with no Subject line.. if you want free help, please care enough about the community to write descriptive Subject lines.]

YES, in most cases it absolutely does need to be the same version, otherwise you are wasting your time.

If you can do an upgrade in place with easyinstall (which would be the best case, if your original installation was done with easyinstall )

First, backup your database!

service citadel stop # or, however you stop citadel

cp /usr/local/citadel/data/* /someplace

THEN, if and only if your "source" installation was installed with easyinstall, you can run easy install again.

[You might want to grab my -k --keep source version of easyinstall, which is a few messages back. It will retain a copy of all the sources in /usr/src for you, with a configured build environment in case you want to build/upgrade again.. ]

After both systems are on the same version, you can use the migration method which has been suggested.

If you CAN'T upgrade, or can't do the migration for whatever reason:

[Check the posts here for various mentions of the "Slacker Method" of migration. It has been discussed recently.]

Essentially, you can setup a client [such as Thunderbird] with access to both systems, then drag your messages into place through the client. 

It's a good time to cleanup and decruft mailboxes anyway, so don't feel like it's really a bad thing.

 

 

Sun Nov 29 2020 10:53:47 AM EST from ParanoidDelusions @ Uncensored

One additional question. In either case, does the source Citadel need to be on the same version as the target Citadel? 

Because upgrading the source Citadel to the latest version is the major hurdle for me, right now. 

 

Thu Nov 26 2020 15:52:16 EST from omatnet @ Uncensored

Here is another option for you, using the "MIGR" parameter of sendcommand:

On the Pi3B do:

sudo /usr/local/citadel/sendcommand -w900 "MIGR export" > ~/CitBackup.xml

Then transfer the xml file to the i5 and there do

sudo /usr/local/citadel/sendcommand -w900 "MIGR import" < ~/CitBackup.xml

The reason for the -w900 is to give the operation enough time (900 seconds = 15 min) to complete, otherwise sendcommand will terminate with its 60s timeout default.

 

If you use ctdlmigrate - it works well, just remember that on the Pi3B you need to allow SSH connection and to permit SSH root user incoming connection. So make sure that a remote root login password is set using 'sudo passwd' (to allow remote root SSH connection you edit /etc/ssh/sshd_config  and make sure that the parameter "PermitRootLogin" is set to "yes"). When done, for security and safety, restore sshd_config to the way it was.

 

 

Wed Nov 25 2020 08:17:37 EST from ParanoidDelusions @ Uncensored

Any one have ideas on how to migrate Citadel from a Pi 3B running Raspbian to an i5 running Debian? 




 



 



 



 



 



[#] Mon Nov 30 2020 10:39:34 EST from warbaby

Subject: Re: Webcit Freeze Requiring Process Kill/Restart

[Reply] [ReplyQuoted] [Headers] [Print]

Does it happen when there are no urlencoded characters in the file name??

Under%2Dthe%2DHarvest%2DMoon%2D16.jpg

It could caused by unescape_input (webcit/utils.c 33), truncating the '%' character.

Also, have a look at the delete_file method in webcit/download.c (297)

 


Mon Nov 30 2020 12:41:58 AM EST from SquareRootSquared @ Uncensored Subject: Re: Webcit Freeze Requiring Process Kill/Restart

 

Sun Nov 29 2020 12:29:21 EST from warbaby @ Uncensored Subject: Re: Webcit Freeze Requiring Process Kill/Restart

You might start by turning on the debugging log, so you can see what's going on.

First stop/kill all your citserver processes.. 

Have a look at /etc/systemd/system/citadel.server OR /etc/init.d/citadel [Wherever your init scripts are..]

Launch citserver with a new log level, something like

/usr/local/citadel/citserver -x 7

(7 is log level 'debug')

See these docs:

Cit Server https://www.citadel.org/citserver.html

Log level [in the system administration manual] https://www.citadel.org/system_administration_manual.html

 

 

Sun Nov 29 2020 07:00:26 AM EST from SquareRootSquared @ Uncensored Subject: Webcit Freeze Requiring Process Kill/Restart

Running Citadel 929 using the recommended easy install method. Setting Lobby to use a file directory, then uploading a file, then trying to delete the file.. causes webcit to emit an error and sometimes freeze requiring a kill/restart of the webcit process. Web browser used is Google Chrome and accessing webcit via http://.



 



 

Done.

Here is the journalctl log snippet (had just tried to delete a picture file named "under the harvest moon.jpg" from the Lobby):

Nov 29 22:59:18 fgnet1.accesslab.com webcit[1026]: webcit[1026]: HTTP: 200 [0.000793] GET /chat_rwho

Nov 29 22:59:18 fgnet1.accesslab.com webcit[1026]: #[0;2;37m#[0;1;31m#[0;2;37mGET /chat_rwho HTTP/1.1#[0m

Nov 29 22:59:18 fgnet1.accesslab.com webcit[1026]: HTTP: 200 [0.000793] GET /chat_rwho

Nov 29 22:59:18 fgnet1.accesslab.com webcit[1026]: webcit[1026]: GET /chat_recv HTTP/1.1

Nov 29 22:59:18 fgnet1.accesslab.com webcit[1026]: webcit[1026]: HTTP: 200 [0.000803] GET /chat_recv

Nov 29 22:59:18 fgnet1.accesslab.com webcit[1026]: #[0;2;37m#[0;1;31m#[0;2;37mGET /chat_recv HTTP/1.1#[0m

Nov 29 22:59:18 fgnet1.accesslab.com webcit[1026]: HTTP: 200 [0.000803] GET /chat_recv

Nov 29 22:59:20 fgnet1.accesslab.com webcit[1026]: webcit[1026]: GET /chat_recv HTTP/1.1

Nov 29 22:59:20 fgnet1.accesslab.com webcit[1026]: webcit[1026]: HTTP: 200 [0.000781] GET /chat_recv

Nov 29 22:59:20 fgnet1.accesslab.com webcit[1026]: #[0;2;37m#[0;1;31m#[0;2;37mGET /chat_recv HTTP/1.1#[0m

Nov 29 22:59:20 fgnet1.accesslab.com webcit[1026]: HTTP: 200 [0.000781] GET /chat_recv

Nov 29 22:59:20 fgnet1.accesslab.com webcit[1026]: webcit[1026]: GET /delete_file?file=Under%2Dthe%2DHarvest%2DMoon%2D16.jpg HTTP/1.1

Nov 29 22:59:20 fgnet1.accesslab.com kernel: webcit[1026]: segfault at a84a0880 ip 00007ff2de308cb4 sp 00007ffca84a06d8 error 6 in libcitadel.so.4.0.925[7ff2de302000+15000]

Nov 29 22:59:20 fgnet1.accesslab.com kernel: Code: 00 00 00 48 83 c4 08 5b 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 90 48 85 ff 74 1b 48 8b 17 48 85 d2 74 13 8b 47 18 85 c0 75 0c <c6> 02 00 48 c7 47 10 00 00 00 00 c3 b8 ff ff ff ff c3 66 2e 0f 1f

Nov 29 22:59:20 fgnet1.accesslab.com citserver[375]: citserver[375]: Citadel client disconnected: ending session.

Nov 29 22:59:20 fgnet1.accesslab.com citserver[375]: citserver[375]: context: [ 12]SRV[citadel-UDS] Session ended.

Nov 29 22:59:20 fgnet1.accesslab.com citserver[375]: citserver[375]: Citadel client disconnected: ending session.

Nov 29 22:59:20 fgnet1.accesslab.com citserver[375]: citserver[375]: context: [ 11]SRV[citadel-UDS] Session ended.

Nov 29 22:59:20 fgnet1.accesslab.com webcit[1026]: #[0;2;37m#[0;1;31m#[0;2;37mGET /delete_file?file=Under%2Dthe%2DHarvest%2DMoon%2D16.jpg HTTP/1.1#[0m

Nov 29 22:59:20 fgnet1.accesslab.com systemd[1]: #[0;1;39m#[0;1;31m#[0;1;39mwebcit-http.service: Main process exited, code=killed, status=11/SEGV#[0m

Nov 29 22:59:20 fgnet1.accesslab.com citserver[375]: Citadel client disconnected: ending session.

Nov 29 22:59:20 fgnet1.accesslab.com systemd[1]: #[0;1;39m#[0;1;31m#[0;1;39mwebcit-http.service: Failed with result 'signal'.#[0m

Nov 29 22:59:20 fgnet1.accesslab.com citserver[375]: context: [ 12]SRV[citadel-UDS] Session ended.

Nov 29 22:59:20 fgnet1.accesslab.com citserver[375]: Citadel client disconnected: ending session.

Nov 29 22:59:20 fgnet1.accesslab.com citserver[375]: context: [ 11]SRV[citadel-UDS] Session ended.

Nov 29 22:59:24 fgnet1.accesslab.com systemd[1]: webcit-http.service: Service RestartSec=3s expired, scheduling restart.

Nov 29 22:59:24 fgnet1.accesslab.com systemd[1]: webcit-http.service: Scheduled restart job, restart counter is at 1.

Nov 29 22:59:24 fgnet1.accesslab.com systemd[1]: Stopped Citadel web service.

Nov 29 22:59:24 fgnet1.accesslab.com systemd[1]: Started Citadel web service.

Nov 29 22:59:24 fgnet1.accesslab.com webcit[1054]: webcit[1054]: Changing directory to /usr/local/webcit/

Nov 29 22:59:24 fgnet1.accesslab.com webcit[1054]: Changing directory to /usr/local/webcit/

Nov 29 22:59:24 fgnet1.accesslab.com webcit[1054]: webcit[1054]: WebCit 926

Nov 29 22:59:24 fgnet1.accesslab.com webcit[1054]: #[0;1;39m#[0;1;31m#[0;1;39mWebCit 926#[0m

Nov 29 22:59:24 fgnet1.accesslab.com webcit[1054]: webcit[1054]: Copyright (C) 1996-2020 by the citadel.org team

Nov 29 22:59:24 fgnet1.accesslab.com webcit[1054]: #[0;1;39m#[0;1;31m#[0;1;39mCopyright (C) 1996-2020 by the citadel.org team#[0m

Nov 29 22:59:24 fgnet1.accesslab.com webcit[1054]: webcit[1054]:

Nov 29 22:59:24 fgnet1.accesslab.com webcit[1054]:

Nov 29 22:59:24 fgnet1.accesslab.com webcit[1054]: webcit[1054]: This program is open source software: you can redistribute it and/or

Nov 29 22:59:24 fgnet1.accesslab.com webcit[1054]: #[0;1;39m#[0;1;31m#[0;1;39mThis program is open source software: you can redistribute it and/or#[0m

Nov 29 22:59:24 fgnet1.accesslab.com webcit[1054]: webcit[1054]: modify it under the terms of the GNU General Public License, version 3.


Here is a snippet from syslog during the same time frame:

Nov 29 22:54:15 fgnet1 kernel: [60156.918691] webcit[857]: segfault at 18a85cc0 ip 00007fc21c0f8cb4 sp 00007fc218a85b18 error 6 in libcitadel.so.4.0.925[7fc21c0f2000+15000]

Nov 29 22:54:15 fgnet1 kernel: [60156.918722] Code: 00 00 00 48 83 c4 08 5b 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 90 48 85 ff 74 1b 48 8b 17 48 85 d2 74 13 8b 47 18 85 c0 75 0c <c6> 02 00 48 c7 47 10 00 00 00 00 c3 b8 ff ff ff ff c3 66 2e 0f 1f

Nov 29 22:59:20 fgnet1 kernel: [60461.992543] webcit[1026]: segfault at a84a0880 ip 00007ff2de308cb4 sp 00007ffca84a06d8 error 6 in libcitadel.so.4.0.925[7ff2de302000+15000]

Nov 29 22:59:20 fgnet1 kernel: [60461.992555] Code: 00 00 00 48 83 c4 08 5b 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 90 48 85 ff 74 1b 48 8b 17 48 85 d2 74 13 8b 47 18 85 c0 75 0c <c6> 02 00 48 c7 47 10 00 00 00 00 c3 b8 ff ff ff ff c3 66 2e 0f 1f

Nov 29 22:59:26 fgnet1 kernel: [60467.622064] webcit[1054]: segfault at b0 ip 0000556dc01c1a76 sp 00007ffc2e641610 error 4 in webcit[556dc01bf000+66000]

Nov 29 22:59:26 fgnet1 kernel: [60467.622076] Code: 00 00 e8 cd e9 ff ff 48 8b 45 e8 48 89 45 e0 e9 91 00 00 00 48 8b 45 d0 8b 80 90 00 00 00 85 c0 0f 84 82 00 00 00 48 8b 45 e8 <8b> 50 30 48 8b 45 d0 8b 80 90 00 00 00 39 c2 75 6d 8b 05 b3 6d 09

I also will try and upload a few pics showing visual effects, please see the upload directory for this room..

 



 



[#] Mon Nov 30 2020 12:20:18 EST from jtbreazeoutlook.com

Subject: Re: Corrupted attachments

[Reply] [ReplyQuoted] [Headers] [Print]

I too, migrated to an old x86 machine, specifically Lubuntu because my x86 machine only has 1gb of Ram, and trying to get Debian in was too much of a hassle for me to want to mess with with my deadline to get it all working. And it does work now, everything is great. I do think it's a Pi issue, since I did both Raspbian and Ubuntu Mate, and it had the same exact issue with no change.

Also, if it helps anyone figure it out, I did migrate using the sendcommand MIGR, and going from the Pi to the x86 machine all the attachments that couldn't be opened before opened as they should, so it seems they weren't corrupted in the database, they were corrupted retrieving them.

Also, eventually I will be on a more stable distro, for sure, I know the issues for being bleeding edge. But at this point my users had been so long without that I needed a quick way to get them going, and installing the latest LTS of Ubuntu in a lightweight GUI was fast. I'm running on 300mb of RAM now.

I never had an issue with the easyinstall, it always went right through, no error messages, and I could migrate my data in, and it worked. Every time, and I went through a lot of installs and devices getting my system going. But, I didn't use the curl method, I used wget.

Sun Nov 29 2020 10:56:33 AM EST from ParanoidDelusions @ Uncensored Subject: Re: Corrupted attachments

 

Tue Nov 24 2020 07:44:55 EST from ParanoidDelusions @ Uncensored Subject: Re: Corrupted attachments

 

Tue Nov 24 2020 02:03:58 ESTfrom jtbreazeoutlook.com @ Uncensored Subject: Re: Corrupted attachments

Great, thanks for the quick reply. I'm liking Ubuntu for the server OS, with the more current repositories, so I'll definitely be staying away from OpenSuse. I'll be keeping an eye on future updates, so I can switch back to the pi, though, it was working great otherwise, there aren't enough users with enough demand to overtax the 4 B, I was sitting at just over 1gb of ram use, and 10% cpu. I'm sold on Citadel, for sure.

 

I mean, ideally we would figure out what the problem is on the Pi - but - building an Intel system might be the best first step. If it happens *there*, it seems to be some kind of operator error. If it doesn't... it is on the Pi architecture or Distro. 

 

By the way, I built out a Citadel on an i86 box, and tested by downloading an image and uploading it as an attachment. 

No square box, no file corruption - you click on the image, and it opens up in a new tab. 

So, this seems like something specific to Pi - possibly to Raspbian. 

 



 



[#] Mon Nov 30 2020 13:06:57 EST from ParanoidDelusions

Subject: Re: Hello, I'm "Whoever" - was Re: Does Migration src and dest need...

[Reply] [ReplyQuoted] [Headers] [Print]

Well, that was probably what I was doing. I thought you downloaded the source, executed ./configure, make and then make upgrade 

Not sure if I misread the instructions on citadel.org - of if they're unclear/out of order. I'll doublecheck when I get home. 

I have written up some documentation on installing Citadel on the Pi. I've got a pretty good test environment now. Once I get everything migrated and the Proxmox running on the public network - I can generate some "Howto" documents that include screenshots and are a little more "inexperienced user" oriented. I think that may help reduce the number of questions that the developers see here. 




Mon Nov 30 2020 10:25:10 EST from warbaby @ Uncensored Subject: Re: Hello, I'm "Whoever" - was Re: Does Migration src and dest need...

No worries, no need for explanations.. I'm just hoping to improve our documentation.

If you used the -k (keep source) version of easyinstall.. and your source is in somthing like

/usr/src/citadel-build-xxx

and then you make some changes..

you want to run

make upgrade

instead of just make.

then

make install

 

 


[#] Mon Nov 30 2020 15:17:04 EST from warbaby

Subject: Re: Hello, I'm "Whoever" - was Re: Does Migration src and dest need...

[Reply] [ReplyQuoted] [Headers] [Print]

First thing: I'll take whatever documentation you have on PI installation.  We're working on all documentation right now..

[txt or preferably markdown would be nice, but html will work if it's clean..]

Regarding the build process...

A few things (regarding compiling) on the website may be out of date, there are also various pages which did not migrate, and which I'm still pulling out of the Wayback Machine (Internet Archive)..

That's why I made the (unofficial) additions to easyinstall.sh

easyinstall as it is will download, compile and then delete all sources.. but with variation (the -k option,) it does not .. it retains everything! ..

all source is left in /usr/src/citadel-build-xxxx

[it's so easy.. ]

it's already configured..

all you have to do is

[clickety clacketly.. edit some files..]

make upgrade

make install

It's much easier than figuring out all the paths and configuration options by hand/brain.

[The actual documentation says "see easyinstall for all configuration options.. "   I just took it one step further, and let easyinstall configure everything for you.]

 

Mon Nov 30 2020 01:06:57 PM EST from ParanoidDelusions @ Uncensored Subject: Re: Hello, I'm "Whoever" - was Re: Does Migration src and dest need...

Well, that was probably what I was doing. I thought you downloaded the source, executed ./configure, make and then make upgrade 

Not sure if I misread the instructions on citadel.org - of if they're unclear/out of order. I'll doublecheck when I get home. 

I have written up some documentation on installing Citadel on the Pi. I've got a pretty good test environment now. Once I get everything migrated and the Proxmox running on the public network - I can generate some "Howto" documents that include screenshots and are a little more "inexperienced user" oriented. I think that may help reduce the number of questions that the developers see here. 




Mon Nov 30 2020 10:25:10 EST from warbaby @ Uncensored Subject: Re: Hello, I'm "Whoever" - was Re: Does Migration src and dest need...

No worries, no need for explanations.. I'm just hoping to improve our documentation.

If you used the -k (keep source) version of easyinstall.. and your source is in somthing like

/usr/src/citadel-build-xxx

and then you make some changes..

you want to run

make upgrade

instead of just make.

then

make install

 

 


 



[#] Mon Nov 30 2020 23:55:59 EST from ParanoidDelusions

Subject: Re: Hello, I'm "Whoever" - was Re: Does Migration src and dest need...

[Reply] [ReplyQuoted] [Headers] [Print]

So... if I seemed quiet tonight, it is because I've been fighting with Raspbian and Debian all night. So, the first thing I did was give up on Proxmox -  for now. I've got a second machine I'm going to go back and test it on and see if I can get it working, once I get over this hurdle. Installed Debian on bare metal. But the Debian box on the same network as the Raspbian Pi. Ctdlmigrate moved over rooms and apparently users - but failed on messages. It seemed to run, then the spinner stalled - and if I looked at dmesg it said that housekeeping wasn't running. Syslog has this in it: 

 

root@tsbbs:/home/donovan# Nov 30 19:09:19 tsbbs citserver[2587]: Out-of-sequence tag <u_flags> detected.  Warning: ODD-DATA!

bash: u_flags: No such file or directory

root@tsbbs:/home/donovan# Nov 30 19:09:19 tsbbs citserver[2587]: Out-of-sequence tag <u_flags> detected.  Warning: ODD-DATA!

bash: u_flags: No such file or directory

root@tsbbs:/home/donovan# Nov 30 19:09:19 tsbbs citserver[2587]: Out-of-sequence tag <u_timescalled> detected.  Warning: ODD-DATA!

bash: u_timescalled: No such file or directory

root@tsbbs:/home/donovan# Nov 30 19:09:19 tsbbs citserver[2587]: Out-of-sequence tag <u_timescalled> detected.  Warning: ODD-DATA!

bash: u_timescalled: No such file or directory

root@tsbbs:/home/donovan# Nov 30 19:09:19 tsbbs citserver[2587]: Out-of-sequence tag <u_posted> detected.  Warning: ODD-DATA!

bash: u_posted: No such file or directory

root@tsbbs:/home/donovan# Nov 30 19:09:19 tsbbs citserver[2587]: Out-of-sequence tag <u_posted> detected.  Warning: ODD-DATA!

bash: u_posted: No such file or directory

root@tsbbs:/home/donovan# Nov 30 19:09:19 tsbbs citserver[2587]: Out-of-sequence tag <u_axlevel> detected.  Warning: ODD-DATA!

bash: u_axlevel: No such file or directory

root@tsbbs:/home/donovan# Nov 30 19:09:19 tsbbs citserver[2587]: Out-of-sequence tag <u_axlevel> detected.  Warning: ODD-DATA!

 


So then I tried the alternate method described above. Same results. No love. It might be that the first attempts hosed Citadel on the target? 

I don't know. The Debian box is all effed up at this point. I'll probably blow it all out and try again. The Raspbian system is still working fine. 

The doc is a .docx word document - with pretty pictures. Very user friendly - but it isn't up to date. I'll upload it here. 


Mon Nov 30 2020 15:17:04 EST from warbaby @ Uncensored Subject: Re: Hello, I'm "Whoever" - was Re: Does Migration src and dest need...

First thing: I'll take whatever documentation you have on PI installation.  We're working on all documentation right now..

[txt or preferably markdown would be nice, but html will work if it's clean..]

Regarding the build process...

A few things (regarding compiling) on the website may be out of date, there are also various pages which did not migrate, and which I'm still pulling out of the Wayback Machine (Internet Archive)..

That's why I made the (unofficial) additions to easyinstall.sh

easyinstall as it is will download, compile and then delete all sources.. but with variation (the -k option,) it does not .. it retains everything! ..

all source is left in /usr/src/citadel-build-xxxx

[it's so easy.. ]

it's already configured..

all you have to do is

[clickety clacketly.. edit some files..]

make upgrade

make install

It's much easier than figuring out all the paths and configuration options by hand/brain.

[The actual documentation says "see easyinstall for all configuration options.. "   I just took it one step further, and let easyinstall configure everything for you.]

 




[#] Tue Dec 01 2020 00:11:17 EST from ParanoidDelusions

[Reply] [ReplyQuoted] [Headers] [Print]

Uploaded the file. I don't see it in the directory. If it didn't make it, let me know, and I'll upload it again. 

 



Go to page: First ... 19 20 21 22 [23] 24 25 26 27 ... Last