Language:
switch to room list switch to menu My folders
Go to page: First ... 9 10 11 12 [13] 14 15 16 17 ... Last
[#] Thu Jan 28 2016 10:11:16 EST from Robert Wolfe @ Neptune

Subject: Telnet Connections

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

Good morning all.

I am having an issue with users not being able to access the BBS via telnet.  I cannot even access it that way if I telnet to localhost.  Is there something I need to do with Citadel in order to make the ANSI side of the system accept inbound telnet connections?



[#] Thu Jan 28 2016 10:20:57 EST from robert @ Neptune

Subject: Re: Telnet Connections

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

2016-01-28 09:11 from Robert Wolfe @neptune
Subject: Telnet Connections
Good morning all.

I am having an issue with users not being able to access the BBS via
telnet.  I cannot even access it that way if I telnet to localhost.
 Is there something I need to do with Citadel in order to make the
ANSI side of the system accept inbound telnet connections?

Ok, looks like I was able to get telnet working by installing telnetd and by creating a user with /usr/local/citadel/citadel as their shell. Something, however, tells me that this is NOT the correct way to do this. Is there something else that I need to be doing instead in order to enable inbound telnet connections to the Citadel server directly instead of going through telnetd?

[#] Thu Jan 28 2016 14:06:44 EST from jame @ Rocasa Mail System

Subject: Re: Testing

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

 

Wed Jan 27 2016 19:51:20 EST from Robert Wolfe @ Neptune Subject: Testing

Ok, just the standard test posting :)

That seems to have gotten around...<g>

Btw; which Citadel version did you install?  On which OS version?  (I'm using Debian for my Citadel installs...)

 

 

Jame

 

 



[#] Thu Jan 28 2016 17:00:05 EST from robert @ Neptune

Subject: Re: Testing

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

2016-01-28 13:06 from jame @rocasa (Rocasa Mail System)
Subject: Re: Testing
 
Wed Jan 27 2016 19:51:20 EST from Robert Wolfe @ Neptune Subject:
Testing



Ok, just the standard test posting :)





That seems to have gotten around...<g>

Btw; which Citadel version did you install?  On which OS version?
 (I'm using Debian for my Citadel installs...)


9.01 is what I am running here in Ubuntu Server. I tried and would have preferred Debian, but decided against it for some reason. I will be darned if I can remember why now. I just know that it appears to be working.

Hmm, Jame. Rocasa. Both sound familiar :) You the same "Jame" from "Rocasa" that is on Fidonet? :)

[#] Sat Jan 30 2016 10:13:16 EST from dothebart @ Uncensored

Subject: Re: CalDAV CalDAV!

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

Still waiting for your patch.

Thu Jan 28 2016 09:13:17 EST from hubertus @ Uncensored Subject: Re: CalDAV CalDAV!

Oh yes, it would !

Wed Jan 27 2016 14:44:05 EST from lol @ Uncensored Subject: CalDAV CalDAV!

CalDav / CardDav Support would be the most awesome thing...



 



 



[#] Sat Jan 30 2016 12:20:45 EST from ibumjr @ Uncensored

Subject: Calendar wrong times

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

When adding event to calendars, they seem to have their own notion of starting times. I mean an 8:00 event gets

entered at 1:00. Any ideas



[#] Thu Jan 28 2016 14:55:25 EST from jame @ Rocasa Mail System

Subject: Re: Telnet Connections

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

 

Thu Jan 28 2016 10:20:57 EST from robert @ Neptune Subject: Re: Telnet Connections
Ok, looks like I was able to get telnet working by installing telnetd and by creating a user with /usr/local/citadel/citadel as their shell. Something, however, tells me that this is NOT the correct way to do this. Is there something else that I need to be doing instead in order to enable inbound telnet connections to the Citadel server directly instead of going through telnetd?

 

 To my knowledge, citadel itself does not have a telnet interface so one has to run a separate telnet daemon. (I generally use the ssl capable version myself in such cases, like the telnetd-ssl pkg in Debian).    And use the citadel text client as the shell for the user...  (Haven't done much testing of that myself, as yet, because I haven't decided which citadel install I'll have as public...)

 

 

Jame

 

 

 



[#] Thu Jan 28 2016 14:56:54 EST from jame @ Rocasa Mail System

Subject: Re: Telnet Connections

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

 

Thu Jan 28 2016 10:11:16 EST from Robert Wolfe @ Neptune Subject: Telnet Connections

  Is there something I need to do with Citadel in order to make the ANSI side of the system accept inbound telnet connections?

 

Have you done any testing using the citadel text mode client?

 

 

 

Jame

 



[#] Sun Jan 31 2016 07:49:08 EST from jame @ Rocasa Mail System

Subject: Re: Testing

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

 

Thu Jan 28 2016 17:00:05 EST from robert @ Neptune Subject: Re: Testing
2016-01-28 13:06 from jame @rocasa (Rocasa Mail System) 
That seems to have gotten around...<g>

Btw; which Citadel version did you install?  On which OS version?
 (I'm using Debian for my Citadel installs...)


9.01 is what I am running here in Ubuntu Server. I tried and would have preferred Debian, but decided against it for some reason. I will be darned if I can remember why now. 

I'd wondered because v9.01 is in Debian Testing ('stretch').   Mind you, there is an issue with the package install (password for initial user doesn't work); but it is available and  does install.   I've set up a new LXC container with Debian Testing installed, and now Citidel, that I'll be using for testing it and related programs...

 

 

 

Jame

 



[#] Sun Jan 31 2016 08:12:27 EST from jame @ Rocasa Mail System

Subject: Fidonet/FTN ...

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

 

Thu Jan 28 2016 17:00:05 EST from robert @ Neptune Subject: Re: Testing
Hmm, Jame. Rocasa. Both sound familiar :) You the same "Jame" from "Rocasa" that is on Fidonet? :)

Yep, that be me...<g>  Been in Fidonet since the early nineties;  starting with Maximus under OS/2 and then going to BBBS (and now MBSE BBS as well) after I changed over to Linux in the mid nineties.  Installed Citadel because it has a BBS history and even though it still needs to be able to import/export FTN messages, it is already useful as it is.

 

 

Jame

 



[#] Mon Feb 01 2016 08:00:17 EST from Freakdog @ Dog Pound BBS II

Subject: Re: Telnet Connections

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

 

Thu Jan 28 2016 10:20:57 AM EST from robert @ Neptune Subject: Re: Telnet Connections
2016-01-28 09:11 from Robert Wolfe @neptune
Subject: Telnet Connections
Good morning all.

I am having an issue with users not being able to access the BBS via
telnet.  I cannot even access it that way if I telnet to localhost.
 Is there something I need to do with Citadel in order to make the
ANSI side of the system accept inbound telnet connections?

Ok, looks like I was able to get telnet working by installing telnetd and by creating a user with /usr/local/citadel/citadel as their shell. Something, however, tells me that this is NOT the correct way to do this. Is there something else that I need to be doing instead in order to enable inbound telnet connections to the Citadel server directly instead of going through telnetd?

This is, indeed, the correct way to do it, if you don't want to lose the ability for you to log in via telnet (though, these days, why anyone anyone keeps telnet going instead of SSH, I've no idea).

If you don't want to be able to log in via telnet, you can look at: http://www.citadel.org/doku.php/faq:installation:how_do_i_get_citadel



[#] Mon Feb 01 2016 14:40:46 EST from tomltpilot @ Uncensored

Subject: relaying denied

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

I get relaying denied.

Running Debian 8.3

 I don't believe the admin login is working correctly as the page looks the same as my other user with Citadel.

ideas?

----



[#] Mon Feb 01 2016 14:54:49 EST from tomltpilot @ Uncensored

Subject: relaying denied

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

I get relaying denied.

Running Debian 8.3

 I don't believe the admin login is working correctly as the page looks the same as my other user with Citadel.

ideas?

----



[#] Mon Feb 01 2016 15:07:00 EST from dothebart @ Uncensored

Subject: Re: relaying denied

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

 

Mon Feb 01 2016 14:54:49 EST from tomltpilot @ Uncensored Subject: relaying denied

I get relaying denied.

Running Debian 8.3

 I don't believe the admin login is working correctly as the page looks the same as my other user with Citadel.

ideas?

----



http://citadel.org/doku.php/?do=search&id=relay

http://citadel.org/doku.php/?do=search&id=aide



[#] Mon Feb 01 2016 15:14:12 EST from tomltpilot @ Uncensored

Subject: relaying denied

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

I get relaying denied.

Running Debian 8.3

 I don't believe the admin login is working correctly as the page looks the same as my other user with Citadel.

ideas?

----



[#] Mon Feb 01 2016 16:03:05 EST from ASCII Express @ Uncensored

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

Hi. I tried building Citadel on Arch Linux using the Easy Install. It crashed when trying to build the text mode client.

In file included from src/ipc_c_tcp.c:25:0:
./src/include/citadel_ipc.h:481:13: warning: inline function 'CtdlIPC_unlock' declared but never defined
INLINE void CtdlIPC_unlock(CtdlIPC *ipc);
^
./src/include/citadel_ipc.h:479:13: warning: inline function 'CtdlIPC_lock' declared but never defined
INLINE void CtdlIPC_lock(CtdlIPC *ipc);
^
src/citadel_ipc.o: In function `CtdlIPCQuit':
/tmp/citadel-build.3035/textclient/src/citadel_ipc.c:267: undefined reference to `CtdlIPC_lock'
/tmp/citadel-build.3035/textclient/src/citadel_ipc.c:281: undefined reference to `CtdlIPC_unlock'
src/citadel_ipc.o: In function `CtdlIPCLogout':
/tmp/citadel-build.3035/textclient/src/citadel_ipc.c:295: undefined reference to `CtdlIPC_lock'
/tmp/citadel-build.3035/textclient/src/citadel_ipc.c:299: undefined reference to `CtdlIPC_unlock'
src/citadel_ipc.o: In function `CtdlIPCPartialRead':
/tmp/citadel-build.3035/textclient/src/citadel_ipc.c:2365: undefined reference to `CtdlIPC_lock'
/tmp/citadel-build.3035/textclient/src/citadel_ipc.c:2383: undefined reference to `CtdlIPC_unlock'
src/citadel_ipc.o: In function `CtdlIPCHighSpeedReadDownload':
/tmp/citadel-build.3035/textclient/src/citadel_ipc.c:2467: undefined reference to `CtdlIPC_lock'
/tmp/citadel-build.3035/textclient/src/citadel_ipc.c:2494: undefined reference to `CtdlIPC_unlock'
src/citadel_ipc.o: In function `CtdlIPCGenericCommand':
/tmp/citadel-build.3035/textclient/src/citadel_ipc.c:2611: undefined reference to `CtdlIPC_lock'
/tmp/citadel-build.3035/textclient/src/citadel_ipc.c:2717: undefined reference to `CtdlIPC_unlock'
collect2: error: ld returned 1 exit status
Makefile:102: recipe for target 'citadel' failed
make: *** [citadel] Error 1
Operating system: Linux 4.3.3-2-ARCH( 4.3.3-2-ARCH x86_64)

[#] Tue Feb 02 2016 02:13:35 EST from jackdeth @ Uncensored

Subject: Citadel config location

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

Somehow all my site-wide configuration got removed, so when citserver starts it complains about everything.

I can reconfigure everything, but for future reference, where is this data stored so I can back it up?  

 

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_fqdn is empty, but must not - check your config!


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_fqdn is empty, but must not - check your config!

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_baseroom is empty, but must not - check your config!


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_baseroom is empty, but must not - check your config!

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_aideroom is empty, but must not - check your config!


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_aideroom is empty, but must not - check your config!

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_twitroom is empty, but must not - check your config!


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_twitroom is empty, but must not - check your config!

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_nodename is empty, but must not - check your config!


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_nodename is empty, but must not - check your config!

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_default_cal_zone is empty, but must not - check your config!


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_default_cal_zone is empty, but must not - check your config!

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_smtp_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 25


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_smtp_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 25

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_pop3_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 110


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_pop3_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 110

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_imap_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 143


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_imap_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 143

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_msa_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 587


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_msa_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 587

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_port_number is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 504


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_port_number is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 504

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_smtps_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 465


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_smtps_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 465

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_pop3s_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 995


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_pop3s_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 995

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_imaps_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 993


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_imaps_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 993

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_pftcpdict_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: -1


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_pftcpdict_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: -1

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_managesieve_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 2020


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_managesieve_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 2020

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_xmpp_c2s_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 5222


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_xmpp_c2s_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 5222

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_xmpp_s2s_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 5269


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_xmpp_s2s_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 5269

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_nntp_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 119


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_nntp_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 119

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_nntps_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 563


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_nntps_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 563

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: citadel should not be configured to run as root! Check the value of c_ctdluid


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:citadel should not be configured to run as root! Check the value of c_ctdluid




[#] Tue Feb 02 2016 21:36:29 EST from jackdeth @ Uncensored

Subject: Re: Citadel config location

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

Can anyone help me out on the answer to this question?  

Much appreciated!

Tue Feb 02 2016 02:13:35 EST from jackdeth @ Uncensored Subject: Citadel config location

Somehow all my site-wide configuration got removed, so when citserver starts it complains about everything.

I can reconfigure everything, but for future reference, where is this data stored so I can back it up?  

 

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_fqdn is empty, but must not - check your config!


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_fqdn is empty, but must not - check your config!

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_baseroom is empty, but must not - check your config!


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_baseroom is empty, but must not - check your config!

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_aideroom is empty, but must not - check your config!


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_aideroom is empty, but must not - check your config!

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_twitroom is empty, but must not - check your config!


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_twitroom is empty, but must not - check your config!

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_nodename is empty, but must not - check your config!


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_nodename is empty, but must not - check your config!

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_default_cal_zone is empty, but must not - check your config!


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_default_cal_zone is empty, but must not - check your config!

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_smtp_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 25


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_smtp_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 25

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_pop3_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 110


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_pop3_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 110

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_imap_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 143


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_imap_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 143

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_msa_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 587


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_msa_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 587

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_port_number is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 504


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_port_number is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 504

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_smtps_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 465


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_smtps_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 465

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_pop3s_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 995


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_pop3s_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 995

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_imaps_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 993


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_imaps_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 993

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_pftcpdict_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: -1


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_pftcpdict_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: -1

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_managesieve_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 2020


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_managesieve_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 2020

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_xmpp_c2s_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 5222


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_xmpp_c2s_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 5222

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_xmpp_s2s_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 5269


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_xmpp_s2s_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 5269

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_nntp_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 119


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_nntp_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 119

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_nntps_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 563


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_nntps_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 563

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: citadel should not be configured to run as root! Check the value of c_ctdluid


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:citadel should not be configured to run as root! Check the value of c_ctdluid




 



[#] Tue Feb 02 2016 21:52:03 EST from "Panagiotis Palias" <panagos81@gmail.com> to citadel_support@citadel.org

Subject: Re: [Citadel Support] Re: Citadel config location

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

Starting from here and following the links you can read more about backup.
http://www.citadel.org/doku.php/faq:systemadmin:what_is_the_best_way_to_backup_my_citadel_installation

Στις 3 Φεβ 2016 03:37, ο χρήστης "jackdeth" <jackdeth@uncensored.citadel.org> έγραψε:

Can anyone help me out on the answer to this question?  

Much appreciated!

Tue Feb 02 2016 02:13:35 EST from jackdeth @ Uncensored Subject: Citadel config location

Somehow all my site-wide configuration got removed, so when citserver starts it complains about everything.

I can reconfigure everything, but for future reference, where is this data stored so I can back it up?  

 

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_fqdn is empty, but must not - check your config!


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_fqdn is empty, but must not - check your config!

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_baseroom is empty, but must not - check your config!


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_baseroom is empty, but must not - check your config!

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_aideroom is empty, but must not - check your config!


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_aideroom is empty, but must not - check your config!

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_twitroom is empty, but must not - check your config!


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_twitroom is empty, but must not - check your config!

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_nodename is empty, but must not - check your config!


Message from syslogd@atlas at Feb  1 23:11:56 ..
 citserver[1515]:configuration setting c_nodename is empty, but must not - check your config!

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_default_cal_zone is empty, but must not - check your config!


Message from syslogd@atlas at Feb  1 23:11:56 ..
 citserver[1515]:configuration setting c_default_cal_zone is empty, but must not - check your config!

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_smtp_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 25


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_smtp_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 25

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_pop3_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 110


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_pop3_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 110

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_imap_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 143


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_imap_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 143

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_msa_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 587


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_msa_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 587

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_port_number is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 504


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_port_number is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 504

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_smtps_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 465


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_smtps_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 465

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_pop3s_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 995


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_pop3s_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 995

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_imaps_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 993


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_imaps_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 993

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_pftcpdict_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: -1


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_pftcpdict_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: -1

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_managesieve_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 2020


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_managesieve_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 2020

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_xmpp_c2s_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 5222


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_xmpp_c2s_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 5222

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_xmpp_s2s_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 5269


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_xmpp_s2s_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 5269

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_nntp_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 119


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_nntp_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 119

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: configuration setting c_nntps_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 563


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:configuration setting c_nntps_port is not -1 (disabled) or a valid TCP-Port - check your config! Default setting is: 563

Broadcast message from systemd-journald@atlas.darksideresearch.com (Mon 2016-02-01 23:11:56 PST):

citserver[1515]: citadel should not be configured to run as root! Check the value of c_ctdluid


Message from syslogd@atlas at Feb  1 23:11:56 ...
 citserver[1515]:citadel should not be configured to run as root! Check the value of c_ctdluid




 



[#] Wed Feb 03 2016 00:57:52 EST from Freejack @ Uncensored

Subject: Fresh Citadel Install on OpenSuse 13.2 using repo homueller

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

I start the service and this is what it does:

citadel.service - Citadel Groupware Server
   Loaded: loaded (/usr/lib/systemd/system/citadel.service; enabled)
   Active: failed (Result: exit-code) since Tue 2016-02-02 23:46:52 CST; 19s ago
  Process: 10190 ExecStart=/usr/sbin/citserver -d -l${CITADEL_LOG_FACILITY} ${CITADEL_DEBUG_AREA} ${CITADEL_HOME_DIR} (code=exited, status=0/SUCCESS)
 Main PID: 10191 (code=exited, status=105)

Feb 02 23:46:51 Server-Linux citserver[10192]: Linked db: Berkeley DB 4.8.30: (May 12, 2014)
Feb 02 23:46:51 Server-Linux citserver[10192]: Calculated dbversion: 4008030
Feb 02 23:46:51 Server-Linux citserver[10192]: Previous dbversion: 0
Feb 02 23:46:51 Server-Linux citserver[10192]: Linked zlib: 1.2.8
Feb 02 23:46:51 Server-Linux citserver[10192]: bdb(): Setting up DB environment
Feb 02 23:46:51 Server-Linux citserver[10192]: dbenv->open(dbenv, /var/lib/citadel/data/, 10899, 0)
Feb 02 23:46:51 Server-Linux citserver[10192]: Starting up DB
Feb 02 23:46:52 Server-Linux citserver[10192]: Checking floor reference counts
Feb 02 23:46:52 Server-Linux citserver[10192]: bdb(): cursor still in progress on cdb 04: can't begin transaction during r/o cursor
Feb 02 23:46:52 Server-Linux citserver[10192]: citserver is stopping in order to prevent data loss. uid=0 gid=0 euid=0 egid=0

 

Went and looked for the folders, it never created the citadel or webcit servers in /usr/local. It did create the ctdlsupport folder. I also tried wiping the data folder in /var/lib/citadel/data and it was a no go.

 

Any ideas?



Go to page: First ... 9 10 11 12 [13] 14 15 16 17 ... Last