Language:
switch to room list switch to menu My folders
Go to page: [1] 2 3 4 5 ... Last
↑↑↑ Old messages ↑↑↑            ↓↓↓ New messages ↓↓↓
[#] Thu May 07 2015 08:32:26 EDT from dothebart @ Uncensored

Subject: Re: Running soooo slow

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

If you have the fulltext index enabled, that will be rebuilt on startup.

sendcommand RWHO

will show you an active context doing that.

Wed May 06 2015 23:22:32 EDT from wylekyote @ Uncensored Subject: Running soooo slow

 

Citadel 8.24-7.5   (at least according to Yum)

 

citserver starts up ok, but is dog slow once it opens the database ..   output lines from the debug to standerr come out 10-15 seconds minimum between each line.    It takes it several minutes for the local command line "citadel" program to return the "name: " prompt and most smtp/imap clients time out before completing their tasks ..   

The "cdb" files have an odd distribution with cdb.08 being 35G and the rest being a few hundred meg to a few bytes (see below) ..  though looking though the backups, its been this size for a while, and the slow phenomena just started this morning.

I did a db_dump | db_load and that seemed to help, but when I restarted the citserver instance the second time, it completely slowed down again.  The machine is basically idle, and the process isn't really accumulating CPU like it would if it was a runaway ..

Nothing really in the log files either..

Thoughts anyone?



[#] Fri May 08 2015 01:23:03 EDT from mendoza @ Uncensored

Subject: Re: [Citadel Support] Re: Can not send a mail.

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

 

Wed May 06 2015 13:05:02 EDT from mendoza @ Uncensored Subject: Re: [Citadel Support] Re: Can not send a mail.

 

Wed May 06 2015 13:02:12 EDT from mendoza @ Uncensored Subject: Re: [Citadel Support] Re: Can not send a mail.

 


Wed May 06 2015 11:52:15 EDT from "Panagiotis Palias" <panagos81@gmail.com> Subject: Re: [Citadel Support] Re: Can not send a mail.
sendcommand is not in the path?
Normally it is symbolic link in /usr/sbin pointing to /usr/lib/citadel-server
You can find it with
find / -name sendcommand

On Tue, May 5, 2015 at 7:41 PM, mendoza <mendoza@uncensored.citadel.org> wrote:

 

Tue May 05 2015 06:28:58 EDT from dothebart @ Uncensored Subject: Re: Can not send a mail.

 

Tue May 05 2015 01:47:43 EDT from mendoza @ Uncensored Subject: Can not send a mail.

Hi,

 

Installed, configured (hope so) citaled server. Bit it does not work correctly. Problem is that i can send and receive mail only from citadel's admin account. I have added two other users, but when i try send mail to these accouts, lets say from Gmail i am getting an error:

The error that the other server returned was:

550 Invalid recipient: testaccount@myserver.bla

 

Ok, i do not have a rDNS record yet, but then i still should be able to receive emails. Furthemore if the problem would be in that record - i think error message would be different. 



please have a look at http://citadel.org/doku.php/faq:troubleshooting:tracking_citadel



Hmmm...

myserver:/ # sendcommand "QDIR testuser@myserver.bla"

sendcommand: command not found

 




--
-p
 
 
 
 

 

Found it:

# find / -name sendcommand
/usr/local/citadel/sendcommand
 
then ran it:
 
myserver:/usr/local/citadel # ./sendcommand "QDIR testuser@myserver.bla"
 
response:
 
sendcommand: started (pid=5563) connecting to Citadel server at /usr/local/citadel/citadel-admin.socket
200 myserver.bla Citadel server ADMIN CONNECTION ready.
QDIR testuser@myserver.bla
200 twstuser @ myserver.bla

sendcommand: processing ended. 

 

 

By the way - somehom citadel server admin receives email, to Aide, not in to Inbox..?



correction:

 

sendcommand: started (pid=5563) connecting to Citadel server at /usr/local/citadel/citadel-admin.socket
200 myserver.bla Citadel server ADMIN CONNECTION ready.
QDIR testuser@myserver.bla
200 testuser @ myserver.bla


But, when i telnet'ing, i get this:

rcpt to: testuser@myserver.bla

550 Invalid recipient: testuser@myserver.bla

rcpt to: admin@myserver.bla

250 RCPT ok <admin@myserver.bla>

 

 



[#] Fri May 08 2015 02:16:06 EDT from dothebart @ Uncensored

Subject: Re: [Citadel Support] Re: Can not send a mail.

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

I've added some more information to that page, please reload & reread ;-)

Fri May 08 2015 01:23:03 EDT from mendoza @ Uncensored Subject: Re: [Citadel Support] Re: Can not send a mail.

 

Wed May 06 2015 13:05:02 EDT from mendoza @ Uncensored Subject: Re: [Citadel Support] Re: Can not send a mail.

 

Wed May 06 2015 13:02:12 EDT from mendoza @ Uncensored Subject: Re: [Citadel Support] Re: Can not send a mail.

 


Wed May 06 2015 11:52:15 EDT from "Panagiotis Palias" <panagos81@gmail.com> Subject: Re: [Citadel Support] Re: Can not send a mail.
sendcommand is not in the path?
Normally it is symbolic link in /usr/sbin pointing to /usr/lib/citadel-server
You can find it with
find / -name sendcommand

On Tue, May 5, 2015 at 7:41 PM, mendoza <mendoza@uncensored.citadel.org> wrote:
 
 
 
 

 



[#] Fri May 08 2015 13:44:41 EDT from mendoza @ Uncensored

Subject: Re: [Citadel Support] Re: Can not send a mail.

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

Ok, i did that :) i have rebuilt the database - no result. Which part exactly should i read and try? :)


i will try to summarize how the server behaves:

I can not receive email to any account except postmaster (citadel admin), therefore, new mail goes not to postmasters inbox, but to Aide room. 

I can connect to server with email client (using Kmail on Ubuntu) i can refresh folders, receiving new adresses, but when i try to send (from any account) i have an error, something like (socket operation time out).

 

when sending from, for example Gmail to my server i have a bounce: 

The error that the other server returned was:
550 Invalid recipient: user@server.bla
 

I can not send mail from ANY account including postmaster. When sending from webcit (any account), it shows "Message has been sent", but if to look at SMTP queue:

 

1) Connection failure: Connection broken during SMTP conversation while talking to gmail-smtp-in.l.google.com; 2) Connection failure: Connection broken during SMTP conversation while talking to gmail-smtp-in.l.google.com; 3) Connection failure: Connection broken during SMTP conversation while talking to alt1.gmail-smtp-in.l.google.com; 4) Connection failure: Connection broken during SMTP conversation while talking to alt1.gmail-smtp-in.l.google.com; 5) Connection failure: Connection broken during SMTP conversation while talking to alt2.gmail-smtp-in.l.google.com; 6) Connection failure: Connection broken during SMTP conversation while talking to alt2.gmail-smtp-in.l.google.com; 7) Connection failure: Connection broken during SMTP conversation while talking to alt3.gmail-smtp-in.l.google.com; 8) Connection failure: Connection broken during SMTP conversation while talking to alt3.gmail-smtp-in.l.google.com; 9) Connection failure: Connection broken during SMTP conversation while talking to alt4.gmail-smtp-in.l.google.com; 10) Connection failure: Connection broken during SMTP conversation while talking to alt4.gmail-smtp-in.l.google.com

 

 

service status:

server:~ # service citadel status

citadel.service - LSB: Start daemon at boot time

   Loaded: loaded (/etc/init.d/citadel)

   Active: active (running) since Pn 2015-05-08 19:29:19 EEST; 25min ago

  Process: 739 ExecStart=/etc/init.d/citadel start (code=exited, status=0/SUCCESS)

   CGroup: /system.slice/citadel.service

           |-800 /usr/local/citadel/citserver -d -h/usr/local/citadel

           `-801 /usr/local/citadel/citserver -d -h/usr/local/citadel

 

Geg 08 19:54:59 server citserver[801]: SMTPCQ: processing outbound queue

Geg 08 19:54:59 server citserver[801]: SMTPCQ: Msg No 142: already in progress!

Geg 08 19:54:59 server citserver[801]: SMTPCQ: Msg No 143: already in progress!

Geg 08 19:54:59 server citserver[801]: SMTPCQ: Msg No 172: already in progress!

Geg 08 19:54:59 server citserver[801]: SMTPCQ: Msg No 176: already in progress!

Geg 08 19:54:59 server citserver[801]: SMTPCQ: queue run completed; 5 messages processed 0 activated

Geg 08 19:54:59 server citserver[801]: network: no neighbor nodes are configured - not polling.

Geg 08 19:54:59 server citserver[801]: No external notifiers configured on system/user

Geg 08 19:54:59 server citserver[801]: W Context: Scheduled 3 idle sessions for termination

Geg 08 19:54:59 server citserver[801]: -- db checkpoint --

 
server:~ # service webcit status
webcit.service
   Loaded: loaded (/etc/init.d/webcit)
   Active: active (running) since Pn 2015-05-08 19:29:18 EEST; 27min ago
  Process: 769 ExecStart=/etc/init.d/webcit start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/webcit.service
           |-796 /usr/local/webcit/webcit -D/var/run/webcit.pid -p2000 uds /usr/local/citadel
           `-797 /usr/local/webcit/webcit -D/var/run/webcit.pid -p2000 uds /usr/local/citadel
 
Geg 08 19:41:43 server webcit[797]: ENT0 1|somemail <somemail@gmail.com>|0|4|fr|postmaster|||||postmaster@myserver.bla|
Geg 08 19:41:43 server webcit[797]: ConditionalWholistExpanded() returns 0
Geg 08 19:41:44 server webcit[797]: HTTP: 200 [0.542962] POST dotskip?room=Mail
Geg 08 19:41:44 server webcit[797]: GET /do_template?template=iconbar_user HTTP/1.1
Geg 08 19:41:44 server webcit[797]: HTTP: 200 [0.696527] GET /do_template?template=iconbar_user
Geg 08 19:41:44 server webcit[797]: GET /roommsgs?room=Mail&startmsg=0&stopmsg=499 HTTP/1.1
Geg 08 19:41:44 server webcit[797]: HTTP: 200 [0.011165] GET /roommsgs?room=Mail&startmsg=0&stopmsg=499
Geg 08 19:47:57 server webcit[797]: Timeout session 0
Geg 08 19:47:57 server webcit[797]: Destroying session 0
Geg 08 19:47:57 server webcit[797]: Closing socket 16
 
running processes:
 
server:~ # ps -A |grep cit
  796 ?        00:00:00 webcit
  797 ?        00:00:00 webcit
  800 ?        00:00:00 citserver
  801 ?        00:00:01 citserver
 
server:/usr/local/citadel # ps -eaf |grep cit
root       796     1  0 19:29 ?        00:00:00 /usr/local/webcit/webcit -D/var/run/webcit.pid -p2000 uds /usr/local/citadel
root       797   796  0 19:29 ?        00:00:00 /usr/local/webcit/webcit -D/var/run/webcit.pid -p2000 uds /usr/local/citadel
root       800     1  0 19:29 ?        00:00:00 /usr/local/citadel/citserver -d -h/usr/local/citadel
root       801   800  0 19:29 ?        00:00:03 /usr/local/citadel/citserver -d -h/usr/local/citadel
root      2146  1604  0 19:53 pts/0    00:00:00 /bin/bash /sbin/service citadel status
root      2151  2146  0 19:54 pts/0    00:00:00 systemctl status --full citadel.service
root      2405  2254  0 20:43 pts/3    00:00:00 grep --color=auto cit
 
 
 
process tree:
 
server:~ # pstree -p |grep cit
           |-citserver(800)---citserver(801)-+-{citserver}(985)
           |                                 |-{citserver}(986)
           |                                 |-{citserver}(988)
           |                                 |-{citserver}(989)
           |                                 `-{citserver}(1369)
           |-webcit(796)---webcit(797)-+-{webcit}(861)
           |                           |-{webcit}(1352)
           |                           |-{webcit}(1355)
           |                           |-{webcit}(2042)
           |                           |-{webcit}(2043)
           |                           |-{webcit}(2044)
           |                           `-{webcit}(2045) 

 

Sendcommand:

server:/usr/local/citadel # ./sendcommand "QDIR user@server.bla"

sendcommand: started (pid=2286) connecting to Citadel server at /usr/local/citadel/citadel-admin.socket

200 techto.lt Citadel server ADMIN CONNECTION ready.

QDIR user@server.bla

200 user @ server.bla

sendcommand: processing ended.

Same with all accounts.

Telnet:

server:/usr/local/citadel # telnet localhost 25

Trying 127.0.0.1...

Connected to localhost.

Escape character is '^]'.

220 techto.lt ESMTP Citadel server ready.

mail from: somegmailuser@gmail.com

250 Sender ok

rcpt to: user@server.bla

550 Invalid recipient: user@server.bla

 

 

 

 

 

Fri May 08 2015 02:16:06 EDT from dothebart @ Uncensored Subject: Re: [Citadel Support] Re: Can not send a mail.

I've added some more information to that page, please reload & reread ;-)

 



 



[#] Sun May 10 2015 18:16:28 EDT from markus @ Uncensored

Subject: Citadel cannot be connected after some time

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

Hello Citadel Support,

 

I'm running Citadel on Debian 7.

My problem is, that Citadel runs for some hours without any obvious problem (mails getting delivered both ways) and then Citadel gets inaccessable by any email client that I use (WebCit, Thunderbird and TypeMail). When I restart citadel, it runs again without problems and all clients can connect, but after a couple of hours the cycle starts over again.

I have already exported and reimported my database in order to be sure it is not a problem with a corrupted database. But that seems not be the case, because the problem was still there.

Does anybody has any idea what's going on? And: Where can I find usefull log files?

 

Thank you very much in advance!

Markus

 

 



[#] Thu May 14 2015 10:00:50 EDT from Freakdog @ Dog Pound BBS II

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

I'm not experiencing this on my system (CentOS 6), but Cascade (Debian 6.0.10)...both installed/upgraded via EasyInstall.

Frequently, but not always, the RSS aggregator returns messages like this:

[#] Thu May 14 2015 04:40:44 PDT from Citadel @

Subject: RSS Aggregation run failure

[Reply] [ReplyQuoted] [Move] [Delete] [Headers] [Print]

Error while RSS-Aggregation Run of http://www.fbi.gov/news/stories/all-stories/rss.xml
need a 200, got a 0 !
Curl Error message: bind failed with errno 22: Invalid argument / Failed binding local connection end
Response text was:

I've done some searching and found pointers to issues with having both an IPv6 address and and IPv4 address on the same adapter. I turned off IPv6 on the system and, while the frequency of these errors has decreased, I'm still seeing them.

Has anyone else run into this? Does anyone have any ideas?



[#] Thu May 14 2015 12:38:44 EDT from one2wonder @ Uncensored

Subject: Getting error 551 - relaying denied when messages sent to citadel

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

Not sure where the relay settings are.  I didn't find much about relaying denied and citadel when searching on google.  Not sure what I did, I reran the setup to set a new admin but nothing seemed related to relaying.  I am just trying to send a message to my user at my domain, I am not trying to actually relay mail.  Also if anyone could point me to where the logs are for citadel that would be helpful.  I had this working and not sure if it was an attempt to install openvpn (doesn't work with my vps) or redoing the setup to change admin that broke this.  I'm running on ubuntu 12.04 - thanks in advance for any advice or help.  - one



[#] Thu May 14 2015 13:09:44 EDT from one2wonder @ Uncensored

Subject: Re: Getting error 551 - relaying denied when messages sent to citadel

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

I found it is just for a particular user, if i create new accounts they work fine.  I tried deleting and recreating the user but no luck.



[#] Thu May 14 2015 13:54:36 EDT from one2wonder @ Uncensored

Subject: Re: Getting error 551 - relaying denied when messages sent to citadel

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

After lots of stopping and starting, changing the citadel node name, changing it back, sendcommand "IGAB" and sendcommand "QDIR address@domain" i got it to work again.  How why I still don't completely understand but at least it works.  /Sigh



[#] Fri May 15 2015 07:15:16 EDT from IGnatius T Foobar @ Uncensored

Subject: Re: Getting error 551 - relaying denied when messages sent to citadel

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

By any chance did you rename your Citadel node at some point? The directory service generally doesn't like when you do that, because all of its entries end up pointing to accounts under the old node name. Re-initializing the global address book with an IGAB command will usually fix that,.

[#] Fri May 15 2015 07:17:15 EDT from dothebart @ Uncensored

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

 

Thu May 14 2015 10:00:50 EDT from Freakdog @ Dog Pound BBS II

I'm not experiencing this on my system (CentOS 6), but Cascade (Debian 6.0.10)...both installed/upgraded via EasyInstall.

Frequently, but not always, the RSS aggregator returns messages like this:

[#] Thu May 14 2015 04:40:44 PDT from Citadel @

Subject: RSS Aggregation run failure

[Reply] [ReplyQuoted] [Move] [Delete] [Headers] [Print]

Error while RSS-Aggregation Run of http://www.fbi.gov/news/stories/all-stories/rss.xml
need a 200, got a 0 !
Curl Error message: bind failed with errno 22: Invalid argument / Failed binding local connection end
Response text was:

I've done some searching and found pointers to issues with having both an IPv6 address and and IPv4 address on the same adapter. I turned off IPv6 on the system and, while the frequency of these errors has decreased, I'm still seeing them.

Has anyone else run into this? Does anyone have any ideas?



if you choose citadels bind address not to be 0.0.0.0 or :: it will put the same as local bind address to curl. Maybe that helps?



[#] Fri May 15 2015 13:08:09 EDT from zeta556 @ Uncensored

Subject: Citadel setup

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

I recently installed citadel alongside nginx on ubuntu 14.0.4

I used apt-get install citadel-suite and went through the installation. Everything seemed to go fine, instead of port 80 i went for 2000.

I tryed entering the portal but it wouldn't connect. So I ssh into my box and try to troubleshoot.

After simply typing in "webcit" command, a prompt starts up.

webcit[11191]: Changing directory to /var/run/citadel/
webcit[11191]: WebCit 8.24
webcit[11191]: Copyright (C) 1996-2014 by the citadel.org team
webcit[11191]: 
webcit[11191]: This program is open source software: you can redistribute it and/or
webcit[11191]: modify it under the terms of the GNU General Public License, version 3.
webcit[11191]: 
webcit[11191]: This program is distributed in the hope that it will be useful,
webcit[11191]: but WITHOUT ANY WARRANTY; without even the implied warranty of
webcit[11191]: MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
webcit[11191]: GNU General Public License for more details.
webcit[11191]: 
webcit[11191]: Found locale: C - en_US
webcit[11191]: locale for ar_AE.UTF8 disabled: No such file or directory
webcit[11191]: locale for bg_BG.UTF8 disabled: No such file or directory
webcit[11191]: locale for cs_CZ.UTF8 disabled: No such file or directory
webcit[11191]: Found locale: en_US.UTF8 - en_US
webcit[11191]: locale for da_DK.UTF8 disabled: No such file or directory
webcit[11191]: locale for de_DE.UTF8 disabled: No such file or directory
webcit[11191]: locale for el_GR.UTF8 disabled: No such file or directory
webcit[11191]: Found locale: en_GB.UTF8 - en_GB
webcit[11191]: locale for es_ES.UTF8 disabled: No such file or directory
webcit[11191]: locale for et_EE.UTF8 disabled: No such file or directory
webcit[11191]: locale for fi_FI.UTF8 disabled: No such file or directory
webcit[11191]: locale for fr_FR.UTF8 disabled: No such file or directory
webcit[11191]: locale for hu_HU.UTF8 disabled: No such file or directory
webcit[11191]: locale for it_IT.UTF8 disabled: No such file or directory
webcit[11191]: locale for ko_KO.UTF8 disabled: No such file or directory
webcit[11191]: locale for nl_NL.UTF8 disabled: No such file or directory
webcit[11191]: locale for pl_PL.UTF8 disabled: No such file or directory
webcit[11191]: locale for pt_BR.UTF8 disabled: No such file or directory
webcit[11191]: locale for ru_RU.UTF8 disabled: No such file or directory
webcit[11191]: locale for zh_CN.UTF8 disabled: No such file or directory
webcit[11191]: locale for he_IL.UTF8 disabled: No such file or directory
webcit[11191]: locale for kk_KK.UTF8 disabled: No such file or directory
webcit[11191]: locale for ro_RO.UTF8 disabled: No such file or directory
webcit[11191]: locale for sl_SL.UTF8 disabled: No such file or directory
webcit[11191]: locale for tr_TR.UTF8 disabled: No such file or directory
webcit[11191]: Text domain: webcit
webcit[11191]: Text domain Charset: UTF8
webcit[11191]: Message catalog directory: /usr/share//locale
webcit[11191]: No Site-local Stylesheet [/usr/share/citadel-webcit/

static.local//webcit.css] installed.
webcit[11191]: Attempting to bind to port 2000...
webcit[11191]: Listening on socket 6
 
Then i log into port 2000 and its working. webcit and citadel is responsive.
Every thing webcit does gets echoed out into the terminal.
Once i close the connection, webcit fails.
Why am I having to type webcit in the terminal for it too work. was the configuration wrong?
H


[#] Fri May 15 2015 14:45:43 EDT from "Panagiotis Palias" <panagos81@gmail.com> to citadel_support@citadel.org

Subject: Re: [Citadel Support] Citadel setup

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

When you run "webcit" in the console and exit with Ctrl-c the program stops. Either you'll run it with "sudo service webcit start" (or "sudo /etc/init.d/webcit start" if the first won't work) or you'll add "&" after the webcit. All commands are to be written without quotation marks.

Στις 15 Μαϊ 2015 7:08 μ.μ., ο χρήστης "zeta556" <zeta556@uncensored.citadel.org> έγραψε:

I recently installed citadel alongside nginx on ubuntu 14.0.4

I used apt-get install citadel-suite and went through the installation. Everything seemed to go fine, instead of port 80 i went for 2000.

I tryed entering the portal but it wouldn't connect. So I ssh into my box and try to troubleshoot.

After simply typing in "webcit" command, a prompt starts up.

webcit[11191]: Changing directory to /var/run/citadel/
webcit[11191]: WebCit 8.24
webcit[11191]: Copyright (C) 1996-2014 by the citadel.org team
webcit[11191]: 
webcit[11191]: This program is open source software: you can redistribute it and/or
webcit[11191]: modify it under the terms of the GNU General Public License, version 3.
webcit[11191]: 
webcit[11191]: This program is distributed in the hope that it will be useful,
webcit[11191]: but WITHOUT ANY WARRANTY; without even the implied warranty of
webcit[11191]: MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
webcit[11191]: GNU General Public License for more details.
webcit[11191]: 
webcit[11191]: Found locale: C - en_US
webcit[11191]: locale for ar_AE.UTF8 disabled: No such file or directory
webcit[11191]: locale for bg_BG.UTF8 disabled: No such file or directory
webcit[11191]: locale for cs_CZ.UTF8 disabled: No such file or directory
webcit[11191]: Found locale: en_US.UTF8 - en_US
webcit[11191]: locale for da_DK.UTF8 disabled: No such file or directory
webcit[11191]: locale for de_DE.UTF8 disabled: No such file or directory
webcit[11191]: locale for el_GR.UTF8 disabled: No such file or directory
webcit[11191]: Found locale: en_GB.UTF8 - en_GB
webcit[11191]: locale for es_ES.UTF8 disabled: No such file or directory
webcit[11191]: locale for et_EE.UTF8 disabled: No such file or directory
webcit[11191]: locale for fi_FI.UTF8 disabled: No such file or directory
webcit[11191]: locale for fr_FR.UTF8 disabled: No such file or directory
webcit[11191]: locale for hu_HU.UTF8 disabled: No such file or directory
webcit[11191]: locale for it_IT.UTF8 disabled: No such file or directory
webcit[11191]: locale for ko_KO.UTF8 disabled: No such file or directory
webcit[11191]: locale for nl_NL.UTF8 disabled: No such file or directory
webcit[11191]: locale for pl_PL.UTF8 disabled: No such file or directory
webcit[11191]: locale for pt_BR.UTF8 disabled: No such file or directory
webcit[11191]: locale for ru_RU.UTF8 disabled: No such file or directory
webcit[11191]: locale for zh_CN.UTF8 disabled: No such file or directory
webcit[11191]: locale for he_IL.UTF8 disabled: No such file or directory
webcit[11191]: locale for kk_KK.UTF8 disabled: No such file or directory
webcit[11191]: locale for ro_RO.UTF8 disabled: No such file or directory
webcit[11191]: locale for sl_SL.UTF8 disabled: No such file or directory
webcit[11191]: locale for tr_TR.UTF8 disabled: No such file or directory
webcit[11191]: Text domain: webcit
webcit[11191]: Text domain Charset: UTF8
webcit[11191]: Message catalog directory: /usr/share//locale
webcit[11191]: No Site-local Stylesheet [/usr/share/citadel-webcit/

static.local//webcit.css] installed.
webcit[11191]: Attempting to bind to port 2000...
webcit[11191]: Listening on socket 6
 
Then i log into port 2000 and its working. webcit and citadel is responsive.
Every thing webcit does gets echoed out into the terminal.
Once i close the connection, webcit fails.
Why am I having to type webcit in the terminal for it too work. was the configuration wrong?
H


[#] Sun May 17 2015 00:30:34 EDT from Freakdog @ Dog Pound BBS II

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

 

Fri May 15 2015 07:17:15 AM EDT from dothebart @ Uncensored

 

Thu May 14 2015 10:00:50 EDT from Freakdog @ Dog Pound BBS II

I'm not experiencing this on my system (CentOS 6), but Cascade (Debian 6.0.10)...both installed/upgraded via EasyInstall.

Frequently, but not always, the RSS aggregator returns messages like this:

[#] Thu May 14 2015 04:40:44 PDT from Citadel @

Subject: RSS Aggregation run failure

[Reply] [ReplyQuoted] [Move] [Delete] [Headers] [Print]

Error while RSS-Aggregation Run of http://www.fbi.gov/news/stories/all-stories/rss.xml
need a 200, got a 0 !
Curl Error message: bind failed with errno 22: Invalid argument / Failed binding local connection end
Response text was:

I've done some searching and found pointers to issues with having both an IPv6 address and and IPv4 address on the same adapter. I turned off IPv6 on the system and, while the frequency of these errors has decreased, I'm still seeing them.

Has anyone else run into this? Does anyone have any ideas?



if you choose citadels bind address not to be 0.0.0.0 or :: it will put the same as local bind address to curl. Maybe that helps?

Just double checked...it is already configured to listen on a specific IP, not a generic.



[#] Mon May 18 2015 14:23:11 EDT from dothebart @ Uncensored

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

 

Thu May 14 2015 10:00:50 EDT from Freakdog @ Dog Pound BBS II

I'm not experiencing this on my system (CentOS 6), but Cascade (Debian 6.0.10)...both installed/upgraded via EasyInstall.

Frequently, but not always, the RSS aggregator returns messages like this:

[#] Thu May 14 2015 04:40:44 PDT from Citadel @

Subject: RSS Aggregation run failure

[Reply] [ReplyQuoted] [Move] [Delete] [Headers] [Print]

Error while RSS-Aggregation Run of http://www.fbi.gov/news/stories/all-stories/rss.xml
need a 200, got a 0 !
Curl Error message: bind failed with errno 22: Invalid argument / Failed binding local connection end
Response text was:

I've done some searching and found pointers to issues with having both an IPv6 address and and IPv4 address on the same adapter. I turned off IPv6 on the system and, while the frequency of these errors has decreased, I'm still seeing them.

Has anyone else run into this? Does anyone have any ideas?



can you revalidate with netstat whether it works out the way its intended?

do you run the latest curl?

Our curl contexts are initialized here:

modules/eventclient/serv_eventclient.c evcurl_init()

So if you want to add debug code or other options, thats the right place.



[#] Mon May 18 2015 20:29:53 EDT from vince-q @ Cascade Lodge BBS

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

Allow me to add that this (the error messages in aide) only started after the most recent Citadel server upgrade. Nothing else has changed.

[#] Tue May 19 2015 17:16:28 EDT from Freakdog @ Dog Pound BBS II

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

 

Mon May 18 2015 02:23:11 PM EDT from dothebart @ Uncensored


[#] Thu May 14 2015 04:40:44 PDT from Citadel @

Subject: RSS Aggregation run failure

[Reply] [ReplyQuoted] [Move] [Delete] [Headers] [Print]

Error while RSS-Aggregation Run of http://www.fbi.gov/news/stories/all-stories/rss.xml
need a 200, got a 0 !
Curl Error message: bind failed with errno 22: Invalid argument / Failed binding local connection end
Response text was:

I've done some searching and found pointers to issues with having both an IPv6 address and and IPv4 address on the same adapter. I turned off IPv6 on the system and, while the frequency of these errors has decreased, I'm still seeing them.

Has anyone else run into this? Does anyone have any ideas?



can you revalidate with netstat whether it works out the way its intended?

do you run the latest curl?

Our curl contexts are initialized here:

modules/eventclient/serv_eventclient.c evcurl_init()

So if you want to add debug code or other options, thats the right place.

I'm afraid I don't understand what you mean by "revalidate with netstat whether it works out the way as intended"

The version of Curl on his Debian system is actually newer than the version on my CentOS 6 system.



[#] Tue May 19 2015 18:37:51 EDT from dothebart @ Uncensored

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

 

Tue May 19 2015 17:16:28 EDTfrom Freakdog @ Dog Pound BBS II
Mon May 18 2015 02:23:11 PM EDTfrom dothebart @ Uncensored


[#]Thu May 14 2015 04:40:44 PDT from Citadel @

Subject: RSS Aggregation run failure

[Reply][ReplyQuoted][Move][Delete] [Headers][Print]

Error while RSS-Aggregation Run of http://www.fbi.gov/news/stories/all-stories/rss.xml
need a 200, got a 0 !
Curl Error message: bind failed with errno 22: Invalid argument / Failed binding local connection end
Response text was:

I've done some searching and found pointers to issues with having both an IPv6 address and and IPv4 address on the same adapter. I turned off IPv6 on the system and, while the frequency of these errors has decreased, I'm still seeing them.

Has anyone else run into this? Does anyone have any ideas?



can you revalidate with netstat whether it works out the way its intended?

do you run the latest curl?

Our curl contexts are initialized here:

modules/eventclient/serv_eventclient.c evcurl_init()

So if you want to add debug code or other options, thats the right place.

I'm afraid I don't understand what you mean by "revalidate with netstat whether it works out the way as intended"

 

root@flunder:~# netstat -alnp

tcp        0      0 192.168.3.111:37249     185.45.5.32:443         ESTABLISHED 3888/iceweasel 

shows open ports, and connected sessions - including their local bind ip.

 

 

The version of Curl on his Debian system is actually newer than the version on my CentOS 6 system.



http://curl.haxx.se/ has 7.42.1

usually one tests the latest version available - this has proven troubles we had nil several times in the past.



[#] Fri May 22 2015 10:25:21 EDT from Freakdog @ Dog Pound BBS II

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

 

Tue May 19 2015 06:37:51 PM EDTfrom dothebart @ Uncensored
Tue May 19 2015 17:16:28 EDTfrom Freakdog @ Dog Pound BBS II
Mon May 18 2015 02:23:11 PM EDTfrom dothebart @ Uncensored


[#]Thu May 14 2015 04:40:44 PDT from Citadel @

Subject: RSS Aggregation run failure

[Reply][ReplyQuoted][Move][Delete] [Headers][Print]

Error while RSS-Aggregation Run of http://www.fbi.gov/news/stories/all-stories/rss.xml
need a 200, got a 0 !
Curl Error message: bind failed with errno 22: Invalid argument / Failed binding local connection end
Response text was:

I've done some searching and found pointers to issues with having both an IPv6 address and and IPv4 address on the same adapter. I turned off IPv6 on the system and, while the frequency of these errors has decreased, I'm still seeing them.

Has anyone else run into this? Does anyone have any ideas?

can you revalidate with netstat whether it works out the way its intended?

do you run the latest curl?

Our curl contexts are initialized here:

modules/eventclient/serv_eventclient.c evcurl_init()

So if you want to add debug code or other options, thats the right place.

I'm afraid I don't understand what you mean by "revalidate with netstat whether it works out the way as intended"

root@flunder:~# netstat -alnp

tcp        0      0 192.168.3.111:37249     185.45.5.32:443         ESTABLISHED 3888/iceweasel 

shows open ports, and connected sessions - including their local bind ip.

mburger@ns1:~$ netstat -alnp | grep :504
(No info could be read for "-p": geteuid()=1001 but you should be root.)
tcp        0      0 69.12.233.235:504       0.0.0.0:*               LISTEN      -              
tcp        0      0 69.12.233.235:58405     108.245.117.203:504     TIME_WAIT   -           get us?

 

The version of Curl on his Debian system is actually newer than the version on my CentOS 6 system.



http://curl.haxx.se/ has 7.42.1

usually one tests the latest version available - this has proven troubles we had nil several times in the past.

Sometimes, this is true. On the other hand, when the currently installed version of curl, which is the latest available for the OS distribution on which Citadel is installed, was functioning just fine with the previous version of Citadel and a new version of Citadel is introduced, one doesn't necessarily point to the version of curl.

One doesn't always upgrade/update system level tools (not libraries, but tools) when upgrading an application that has, until this point, been working just fine with the installed version...but that may just be my 29 years of IT administration talking.



[#] Fri May 22 2015 14:57:38 EDT from dothebart @ Uncensored

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

 

Fri May 22 2015 10:25:21 EDTfrom Freakdog @ Dog Pound BBS II
Tue May 19 2015 06:37:51 PM EDTfrom dothebart @ Uncensored
Tue May 19 2015 17:16:28 EDTfrom Freakdog @ Dog Pound BBS II
Mon May 18 2015 02:23:11 PM EDTfrom dothebart @ Uncensored


[#]Thu May 14 2015 04:40:44 PDT from Citadel @

Subject: RSS Aggregation run failure

[Reply][ReplyQuoted][Move][Delete] [Headers][Print]

Error while RSS-Aggregation Run of http://www.fbi.gov/news/stories/all-stories/rss.xml
need a 200, got a 0 !
Curl Error message: bind failed with errno 22: Invalid argument / Failed binding local connection end
Response text was:

I've done some searching and found pointers to issues with having both an IPv6 address and and IPv4 address on the same adapter. I turned off IPv6 on the system and, while the frequency of these errors has decreased, I'm still seeing them.

Has anyone else run into this? Does anyone have any ideas?

can you revalidate with netstat whether it works out the way its intended?

do you run the latest curl?

Our curl contexts are initialized here:

modules/eventclient/serv_eventclient.c evcurl_init()

So if you want to add debug code or other options, thats the right place.

I'm afraid I don't understand what you mean by "revalidate with netstat whether it works out the way as intended"

root@flunder:~# netstat -alnp

tcp        0      0 192.168.3.111:37249     185.45.5.32:443         ESTABLISHED 3888/iceweasel 

shows open ports, and connected sessions - including their local bind ip.

mburger@ns1:~$ netstat -alnp | grep :504
(No info could be read for "-p": geteuid()=1001 but you should be root.)
tcp        0      0 69.12.233.235:504       0.0.0.0:*               LISTEN      -              
tcp        0      0 69.12.233.235:58405     108.245.117.203:504     TIME_WAIT   -           get us?

 you need to do this when rss feeds are aggregated (and even better, if the error occurs) and identify peers which are on port 80 or 443.

The version of Curl on his Debian system is actually newer than the version on my CentOS 6 system.

http://curl.haxx.se/ has 7.42.1

usually one tests the latest version available - this has proven troubles we had nil several times in the past.

Sometimes, this is true. On the other hand, when the currently installed version of curl, which is the latest available for the OS distribution on which Citadel is installed, was functioning just fine with the previous version of Citadel and a new version of Citadel is introduced, one doesn't necessarily point to the version of curl.

One doesn't always upgrade/update system level tools (not libraries, but tools) when upgrading an application that has, until this point, been working just fine with the installed version...but that may just be my 29 years of IT administration talking.

Versions before citadel may at most have logged these incidents (instead of placing error messages into the aide room), maybe it didn't even that - so you probably never knew it occured while these incidents happened as they do now.

So In this case, doing fingerpointing at libcurl its especialy true:

citadel only sets curl options like the local bind ip (which I told you above) So if you know another curl option to try, I pointed out where these can be changed.

Except for these options, there are only two components involved into establishing connections: libcurl and the kernel. So if you want to hunt it down and try to fix it, you need to swap one of both and hope its fixed.

Another thing to try maybe if you see it happening especialy for one rss server is running tcpdump filtering that and try to identify what happened on the wire...



Go to page: [1] 2 3 4 5 ... Last