Language:
switch to room list switch to menu My folders
Go to page: First ... 18 19 20 21 [22] 23 24 25 26 ... Last
[#] Thu Nov 26 2020 10:07:07 EST from warbaby

Subject: Re: additional set up?

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

You've told us basically nothing.

Any error messages in the console log on startup?

try (as root)

grep citadel /var/log/syslog

or

grep citserver /var/log/syslog

 

Thu Nov 26 2020 09:38:35 AM EST from wesleyallison @ Uncensored Subject: additional set up?

Is there any additional setup that I need to do to get it to work I used easy install and port forward all the ports

I have a No-IP.com domain



 



[#] Thu Nov 26 2020 10:48:09 EST from ParanoidDelusions

Subject: Re: additional set up?

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

Can you connect locally? 

Thu Nov 26 2020 09:38:35 EST from wesleyallison @ Uncensored Subject: additional set up?

Is there any additional setup that I need to do to get it to work I used easy install and port forward all the ports

I have a No-IP.com domain



 



[#] Thu Nov 26 2020 15:52:16 EST from omatnet

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

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? 




 



[#] Fri Nov 27 2020 16:55:41 EST from guesty2k

Subject: Re: STARTTLS

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

Does anyone know how to resolve this? 

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

 

 



[#] Sat Nov 28 2020 10:09:07 EST from ParanoidDelusions

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

The upgrade process isn't totally clear to me: 


Upgrading

Any existing Citadel installation may be upgraded in place without the need to discard your existing data files.

Upgrading to a new version uses the same build procedure as compiling the program for a fresh install, except that you want to do "make upgrade" instead of "make install". This will overwrite the programs but not your data. Be sure to shut down citserver during this process! If Citadel is running while you upgrade, you may face data corruption issues.

After doing make upgrade, you should run setup again to bring your data files up to date. Please see the setup section below for more information on this.


Especially if the Easy-Install was used. 

Easy Install will automatically initialize. Please note that we said "easy," not "fast." It will compile a lot of code and is therefore quite time consuming. In the future we plan to add Docker containers to make it install faster.

So, what's it going to do? When you begin Easy Install, the following things are going to happen:

  • If your Linux distribution is identified, Easy Install will offer to try installing some of the dependencies.
  • Citadel Server, the WebCit front end, the text mode client, and some of the supporting libraries such as Berkeley DB will be downloaded from the Easy Install web site.
  • All packages will be compiled and installed. This will take a long time. Citadel will be installed to /usr/local/citadel, WebCit will be installed to /usr/local/webcit, and the supporting libraries will be installed to /usr/local/ctdlsupport.
  • The setup program will initialize, and you will be asked a few questions about how you want the software configured. You will be offered the opportunity to disable any email and groupware software already installed on your system, and you will be offered the opportunity to have the Citadel services automatically initialized on startup.
  • WebCit will be similarly configured. If you are not running some other web server (such as Nginx or Apache), you can run WebCit on port 80; otherwise, pick some other port.

Which implies that everything runs automatically. 

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?



The Sanitarium is running Citadel 925 with WebCit 925, server build 925

 




[#] Sat Nov 28 2020 12:15:09 EST from SquareRootSquared

Subject: Chat/Instant Messenger send/receive Delay

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

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?



[#] Sat Nov 28 2020 12:20:05 EST from SquareRootSquared

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

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

Forgot to mention that the server and two client machines are all located on the same local LAN and switch so no delays are being caused by operating over the Internet .



[#] Sat Nov 28 2020 12:58:23 EST from SquareRootSquared

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

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

Also forgot to mention that this is while using the WebCit web client, so it's the Citadel Instant Messenger and the Citadel Chat that is being used. The delay seems to be as if Citadel is polling the client inputs on a set schedule, buffering inputs over the interval, and then sending at preset intervals? Rather than an asynchronous operation? If so, can the polling interval be shortened?

 

 

 



[#] Sat Nov 28 2020 13:40:55 EST from platonov

Subject: Re: Problem with incorrect displaying of Subject: header fixed

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

There is a new glitch related to displaying of Subject: header. It happens on one of the feeds that initially worked fine after "da fix".

But now they have changed some things and subject header does not display in most of the articles. What it displays is "(no subject)" string.

Yes, that feed is screwed up and records look weird. But the problem is that how come citadel reports it as empty string when it is not.

Interestingly enough, when the same articles are viewed using Thunderbird and IMAP account, it all looks fine, including their screwed up From: header.

This happens when you view the article in the Mail Folder format ONLY.

But subject header is actually not empty and it IS being displayed correctly in Bulletin Board and Blog formats.

The RSS feed is:

<a href="https://www.vtimes.io/rss">Vtimes</a>

In the sources, using cscope, I can see 3 instances of producing the "(no subject)" string. Here they are:

   File                           Line
0 serv_netmail.c          132    Subject = NewStrBufPlain(HKEY("(no subject)"));
1 msgbase.c              1888    cprintf("Subject: (no subject)%s", nl);
2 mailview_renderer.c   72    StrBufAppendBufPlain(Msg->subj, _("(no subject)"), -1,0);

 

Mon Nov 09 2020 09:54:19 EST from IGnatius T Foobar @ Uncensored Subject: Re: Problem with incorrect displaying of Subject: header fixed
Sure thing. I understand the problem but I want to make sure I'm getting the fix correct. I have code up in the editor but if yours works I'll review that and use it instead.

You're correct in observing that serv_rssclient.c is a substantial rewrite.
A few years ago we made a decision to simplify all of the pollers by letting libcurl do all the work. This allowed us to remove thousands of lines of code and two external dependencies. RFC2047-encoding of header fields is definitely something that was overlooked, so I'm glad you have brought it to our attention.

 



[#] Sat Nov 28 2020 14:11:29 EST from ParanoidDelusions

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

The Easy-Install doesn't seem to work with Raspbian or Debian at this point - even following the instructions I used last time I installed on a Pi - and the repo package runs setup but doesn't work, either - unsurprisingly. 

I don't have time to REALLY dig in right now, because of Thanksgiving - and I've got a feeling I'll be re-familiarized with a lot of the things I've forgotten from getting it installed on Raspbian the first time around. 

I basically get this error: 

 

 

My document mentions I might have ran easy-install under Sh instead of Bash. That returns... 

 

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. 

 



[#] Sat Nov 28 2020 22:01:23 EST from ParanoidDelusions

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

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 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. 

 



 



 



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