You're welcome Art.. It's my pleasure. to help out.
My last thought on this one at the moment should be in a new thread though..
The /tmp/citadel-install.log file.. easyinstall is not in the main repos that I can see.. so I couldn't check the git log for that.
I think the bash trace will help out. But, I distinctly recall that handy message from easy install
"something has failed.. you might look in /tmp/citadel-install.log" or something like that.
Mon Jun 15 2020 10:49:34 PM EDT from IGnatius T Foobar @ Uncensored Subject: Re: sieve2_license errorThank you warbaby for the excellent insight and help.
I will echo the request for our OpenSuSE friends to post the completed diffs to the Easy Install script to make it run properly on OpenSuSE. We will cheerfully accept any changes that are needed. It's just that we don't have anyone on the core team that uses this distribution so we don't normally test with it.
In the future we will have a Docker container for Citadel and I hope most people will use that.
Mon Jun 15 2020 05:21:10 PM EDT from warbaby @ Uncensored Subject: Re: sieve2_license errorI encourage you to keep cracking away at it. It's probably just a path.. You might need to add symlink. I have some other stuff todo for a while, but am still monitoring the thread.
Subject: Re: BerkeleyDB lib error ...-- sieve2_license error
bgerum2 it's ok. If that is the case then it's alright. It just came over the wrong way, you know, the road to heaven is littered with good intentions :) Be careful next time mate, cheers
Mon Jun 15 2020 15:41:31 EDT from bgerum2 @ Uncensored Subject: Re: BerkeleyDB lib error ...-- sieve2_license errorHi easy now, sorry, I just wanted to help you, I think both problems are connected so I edited the subject. But I probably should have started a new thread.
Subject: Re: BerkeleyDB lib error while installing with Easy Install
Thanks for your reply warbaby. I appreciate it.
So, I ran the "wget http://easyinstall.citadel.org/install...." from inside usr/local/ to download the easyinstall.sh but could find the file anywhere.
Where did wget save the easyinstall.sh file please?
Thanks
Mon Jun 15 2020 11:34:47 EDT from warbaby @ Uncensored Subject: Re: BerkeleyDB lib error while installing with Easy InstallI was talking strictly about easyinstall, the package retrieval for SUSE was left for another day.. I am not aware of packages for SUSE.. but that doesn't mean they don't exist.
try this..
wget http://easyinstall.citadel.org/install -O easyinstall.sh
chmod+x easyinstall.sh
edit the top line to
#!/bin/bash -x
run it and see what is happening..
You might be benefited by the other conversation also.
Perpetuating that hijacking was probably my fault.. I did edit the subject line when I replied, but yes it should have been a new thread.. My apology for that.
But.. You might both be having the same issue, (seems like a string/path thing..) and can benefit by working together to complete that section of easy install.
Subject: Re: BerkeleyDB lib error while installing with Easy Install
I would run that from your home directory or ~/bin if you have a "bin" in your home directory and path.
if you run
wget http://easyinstall.citadel.org/install
The file name will be 'install' and will appear in the directory you ran the command from. pwd
If you run
wget http://easyinstall.citadel.org/install -O easyinstall.sh chmod +x easyinstall.sh
That will help you identify the file later on, also so things like syntax highlighting work.
Tue Jun 16 2020 12:28:11 PM EDT from easy now @ Uncensored Subject: Re: BerkeleyDB lib error while installing with Easy Install
Thanks for your reply warbaby. I appreciate it.
So, I ran the "wget http://easyinstall.citadel.org/install...." from inside usr/local/ to download the easyinstall.sh but could find the file anywhere.
Where did wget save the easyinstall.sh file please?
Thanks
Mon Jun 15 2020 11:34:47 EDT from warbaby @ Uncensored Subject: Re: BerkeleyDB lib error while installing with Easy InstallI was talking strictly about easyinstall, the package retrieval for SUSE was left for another day.. I am not aware of packages for SUSE.. but that doesn't mean they don't exist.
try this..
wget http://easyinstall.citadel.org/install -O easyinstall.sh
chmod+x easyinstall.sh
edit the top line to
#!/bin/bash -x
run it and see what is happening..
You might be benefited by the other conversation also.
Perpetuating that hijacking was probably my fault.. I did edit the subject line when I replied, but yes it should have been a new thread.. My apology for that.
But.. You might both be having the same issue, (seems like a string/path thing..) and can benefit by working together to complete that section of easy install.
I was going to spin up a vps for this, but am finding openSUSE images hard to come by with my regular vps providers.. Also, all local resources to install it are tied up at the moment.
I'm mainly writing this to encourage those of you with an interest in it. openSUSE to keep pushing ahead on this..
It would be great to have this support in the installer.. But you guys are the only ones with a working openSUSE environment..
So, . . Keep up the good work! Just use basic troubleshooting skills, converse and share. I will try to help, but mainly.. It is in your hands...
Thanks,
-Warren
Subject: unsubscribe
How does one unsubscribe from this mail list?
Thank you.
http://uncensored.citadel.org/listsub
Tue Jun 16 2020 12:47:44 PM EDT from "juanhernandez98" <juanhernandez98@gmail.com> Subject: unsubscribeHello All,
How does one unsubscribe from this mail list?
Thank you.
I didn't work with vps yet, but here are openSUSE images:
https://download.opensuse.org/repositories/Cloud:/Images:/Leap_15.1/images/
Tue Jun 16 2020 12:45:48 EDT from warbaby @ Uncensored Subject: openSUSE and easyinstall..I was going to spin up a vps for this, but am finding openSUSE images hard to come by with my regular vps providers.. Also, all local resources to install it are tied up at the moment.
I'm mainly writing this to encourage those of you with an interest in it. openSUSE to keep pushing ahead on this..
It would be great to have this support in the installer.. But you guys are the only ones with a working openSUSE environment..
So, . . Keep up the good work! Just use basic troubleshooting skills, converse and share. I will try to help, but mainly.. It is in your hands...
Thanks,
-Warren
Hello everyone, I'm new to Citadel. I've installed and have it running on my Raspberry pi, I am able to recieve emails, but can't send, and I can't seem to get it working on any other apps, like outlook, thunderbird, etc. Anyone have any ideas?
I can see port 25 is being blocked, I'm trying to use the smart host feature (smtp.verizon.net) with no success.
I forced the installation of libsieve by inserting OLDSUM=does_not_exist in line 445 in the installer.
it did install fine:
gmake[2]: Entering directory '/tmp/citadel-build.13687/libsieve-2.2.7/src/sv_include'
gmake[2]: Nothing to be done for 'install-exec-am'.
test -z "/usr/local/ctdlsupport/include" || /usr/bin/mkdir -p "/usr/local/ctdlsupport/include"
/usr/bin/install -c -m 644 'sieve2.h' '/usr/local/ctdlsupport/include/sieve2.h'
/usr/bin/install -c -m 644 'sieve2_error.h' '/usr/local/ctdlsupport/include/sieve2_error.h'
gmake[2]: Leaving directory '/tmp/citadel-build.13687/libsieve-2.2.7/src/sv_include'
gmake[1]: Leaving directory '/tmp/citadel-build.13687/libsieve-2.2.7/src/sv_include'
Complete.
but now I'm back with the license error:
checking sieve2.h usability... yes
checking sieve2.h presence... yes
checking for sieve2.h... yes
checking for sieve2_license in -lsieve... no
configure: error: libsieve was not found and is required. More info: http://www.citadel.org/doku.php/installation:start
Citadel Easy Install is aborting.
Tue Jun 16 2020 11:13:54 EDT from warbaby @ Uncensored Subject: Re: sieve2_license errorYou're welcome Art.. It's my pleasure. to help out.
My last thought on this one at the moment should be in a new thread though..
The /tmp/citadel-install.log file.. easyinstall is not in the main repos that I can see.. so I couldn't check the git log for that.
I think the bash trace will help out. But, I distinctly recall that handy message from easy install
"something has failed.. you might look in /tmp/citadel-install.log" or something like that.
Mon Jun 15 2020 10:49:34 PM EDT from IGnatius T Foobar @ Uncensored Subject: Re: sieve2_license errorThank you warbaby for the excellent insight and help.
I will echo the request for our OpenSuSE friends to post the completed diffs to the Easy Install script to make it run properly on OpenSuSE. We will cheerfully accept any changes that are needed. It's just that we don't have anyone on the core team that uses this distribution so we don't normally test with it.
In the future we will have a Docker container for Citadel and I hope most people will use that.
Mon Jun 15 2020 05:21:10 PM EDT from warbaby @ Uncensored Subject: Re: sieve2_license errorI encourage you to keep cracking away at it. It's probably just a path.. You might need to add symlink. I have some other stuff todo for a while, but am still monitoring the thread.
Here's a script for you.. (should be safe eg.. "interactive", I did run it on my box, but you might want to ls -al those filenames first.. my eyes are really sore right now.. )
# cause-easyinstall-to-download-packages-again.sh
#!/bin/bash -x
rm -i /usr/local/ctdlsupport/etc/*.sum
rm -i /usr/local/citadel/*.sum
rm -i /usr/local/webcit/*.sum
This should probably be an option in easyinstall someday..
I'll reply separately on the configure script.
Wed Jun 17 2020 06:16:16 PM EDT from bgerum2 @ Uncensored Subject: Re: sieve2_license errorI forced the installation of libsieve by inserting OLDSUM=does_not_exist in line 445 in the installer.
it did install fine:
gmake[2]: Entering directory '/tmp/citadel-build.13687/libsieve-2.2.7/src/sv_include'
gmake[2]: Nothing to be done for 'install-exec-am'.
test -z "/usr/local/ctdlsupport/include" || /usr/bin/mkdir -p "/usr/local/ctdlsupport/include"
/usr/bin/install -c -m 644 'sieve2.h' '/usr/local/ctdlsupport/include/sieve2.h'
/usr/bin/install -c -m 644 'sieve2_error.h' '/usr/local/ctdlsupport/include/sieve2_error.h'
gmake[2]: Leaving directory '/tmp/citadel-build.13687/libsieve-2.2.7/src/sv_include'
gmake[1]: Leaving directory '/tmp/citadel-build.13687/libsieve-2.2.7/src/sv_include'
Complete.but now I'm back with the license error:
checking sieve2.h usability... yes
checking sieve2.h presence... yes
checking for sieve2.h... yes
checking for sieve2_license in -lsieve... no
configure: error: libsieve was not found and is required. More info: http://www.citadel.org/doku.php/installation:start
Citadel Easy Install is aborting.
Tue Jun 16 2020 11:13:54 EDT from warbaby @ Uncensored Subject: Re: sieve2_license errorYou're welcome Art.. It's my pleasure. to help out.
My last thought on this one at the moment should be in a new thread though..
The /tmp/citadel-install.log file.. easyinstall is not in the main repos that I can see.. so I couldn't check the git log for that.
I think the bash trace will help out. But, I distinctly recall that handy message from easy install
"something has failed.. you might look in /tmp/citadel-install.log" or something like that.
Mon Jun 15 2020 10:49:34 PM EDT from IGnatius T Foobar @ Uncensored Subject: Re: sieve2_license errorThank you warbaby for the excellent insight and help.
I will echo the request for our OpenSuSE friends to post the completed diffs to the Easy Install script to make it run properly on OpenSuSE. We will cheerfully accept any changes that are needed. It's just that we don't have anyone on the core team that uses this distribution so we don't normally test with it.
In the future we will have a Docker container for Citadel and I hope most people will use that.
Mon Jun 15 2020 05:21:10 PM EDT from warbaby @ Uncensored Subject: Re: sieve2_license errorI encourage you to keep cracking away at it. It's probably just a path.. You might need to add symlink. I have some other stuff todo for a while, but am still monitoring the thread.
Okay, I had to find a recent build dir in /tmp..
So, here's the question..
did you run easyinstall with trace on (eg #!/bin/bash -x on first line),
and if so, what did your configure line look like? [it may be another double-quote situation..]
I did it manually, and it worked fine.
so try it.. (your build number will be different)..
then post your results..
[problem may not be here at all.. may be install options.]
root@ftp:/tmp/citadel-build.2704/libsieve-2.2.7/src# ./configure --prefix=/usr/local/ctdlsupport
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for a BSD-compatible install... /usr/bin/install -c
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/bin/ld option to reload object files... -r
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for ANSI C header files... (cached) yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking for unistd.h... (cached) yes
checking alloca.h usability... yes
checking alloca.h presence... yes
checking for alloca.h... yes
checking for an ANSI C-conforming const... yes
checking for size_t... yes
checking whether byte ordering is bigendian... no
checking endian.h usability... yes
checking endian.h presence... yes
checking for endian.h... yes
checking for working memcmp... yes
checking for vprintf... yes
checking for _doprnt... no
configure: creating ./config.status
config.status: creating libsieve.pc
config.status: creating sv_parser/Makefile
config.status: creating sv_regex/Makefile
config.status: creating sv_interface/Makefile
config.status: creating sv_util/Makefile
config.status: creating sv_test/Makefile
config.status: creating sv_include/Makefile
config.status: creating Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
Wed Jun 17 2020 06:16:16 PM EDT from bgerum2 @ Uncensored Subject: Re: sieve2_license errorI forced the installation of libsieve by inserting OLDSUM=does_not_exist in line 445 in the installer.
it did install fine:
gmake[2]: Entering directory '/tmp/citadel-build.13687/libsieve-2.2.7/src/sv_include'
gmake[2]: Nothing to be done for 'install-exec-am'.
test -z "/usr/local/ctdlsupport/include" || /usr/bin/mkdir -p "/usr/local/ctdlsupport/include"
/usr/bin/install -c -m 644 'sieve2.h' '/usr/local/ctdlsupport/include/sieve2.h'
/usr/bin/install -c -m 644 'sieve2_error.h' '/usr/local/ctdlsupport/include/sieve2_error.h'
gmake[2]: Leaving directory '/tmp/citadel-build.13687/libsieve-2.2.7/src/sv_include'
gmake[1]: Leaving directory '/tmp/citadel-build.13687/libsieve-2.2.7/src/sv_include'
Complete.but now I'm back with the license error:
checking sieve2.h usability... yes
checking sieve2.h presence... yes
checking for sieve2.h... yes
checking for sieve2_license in -lsieve... no
configure: error: libsieve was not found and is required. More info: http://www.citadel.org/doku.php/installation:start
Citadel Easy Install is aborting.
Tue Jun 16 2020 11:13:54 EDT from warbaby @ Uncensored Subject: Re: sieve2_license errorYou're welcome Art.. It's my pleasure. to help out.
My last thought on this one at the moment should be in a new thread though..
The /tmp/citadel-install.log file.. easyinstall is not in the main repos that I can see.. so I couldn't check the git log for that.
I think the bash trace will help out. But, I distinctly recall that handy message from easy install
"something has failed.. you might look in /tmp/citadel-install.log" or something like that.
Mon Jun 15 2020 10:49:34 PM EDT from IGnatius T Foobar @ Uncensored Subject: Re: sieve2_license errorThank you warbaby for the excellent insight and help.
I will echo the request for our OpenSuSE friends to post the completed diffs to the Easy Install script to make it run properly on OpenSuSE. We will cheerfully accept any changes that are needed. It's just that we don't have anyone on the core team that uses this distribution so we don't normally test with it.
In the future we will have a Docker container for Citadel and I hope most people will use that.
Mon Jun 15 2020 05:21:10 PM EDT from warbaby @ Uncensored Subject: Re: sieve2_license errorI encourage you to keep cracking away at it. It's probably just a path.. You might need to add symlink. I have some other stuff todo for a while, but am still monitoring the thread.
Did you try this procedure?
http://www.citadel.org/doku.php?id=faq:troubleshooting:outbound_mail
Tue Jun 16 2020 11:40:37 PM EDT from gotcubed @ Uncensored Subject: Re: Setting up on Raspberry PiI can see port 25 is being blocked, I'm trying to use the smart host feature (smtp.verizon.net) with no success.
Subject: Re: BerkeleyDB lib error while installing with Easy Install
Ok. Thanks.
So far..
My script stayed alive after answering yes to letting it install dependencies. It went ahead and downloaded and install all including the elusive berkeleydb and webcit. But it aborted at the last huddle trying to connect to a running Citadel server.
Error: Setup could not connect to a running Citadel server.: No such file or directory /usr/local/citadel/citadel-admin.socket.
The question is 'am I missing something? should I attempt to start citadel and webcit even with this error? and would they start?
Tue Jun 16 2020 12:39:15 EDT from warbaby @ Uncensored Subject: Re: BerkeleyDB lib error while installing with Easy InstallI would run that from your home directory or ~/bin if you have a "bin" in your home directory and path.
if you run
wget http://easyinstall.citadel.org/installThe file name will be 'install' and will appear in the directory you ran the command from. pwd
If you run
wget http://easyinstall.citadel.org/install -O easyinstall.sh chmod +x easyinstall.shThat will help you identify the file later on, also so things like syntax highlighting work.
Tue Jun 16 2020 12:28:11 PM EDT from easy now @ Uncensored Subject: Re: BerkeleyDB lib error while installing with Easy Install
Thanks for your reply warbaby. I appreciate it.
So, I ran the "wget http://easyinstall.citadel.org/install...." from inside usr/local/ to download the easyinstall.sh but could find the file anywhere.
Where did wget save the easyinstall.sh file please?
Thanks
Mon Jun 15 2020 11:34:47 EDT from warbaby @ Uncensored Subject: Re: BerkeleyDB lib error while installing with Easy InstallI was talking strictly about easyinstall, the package retrieval for SUSE was left for another day.. I am not aware of packages for SUSE.. but that doesn't mean they don't exist.
try this..
wget http://easyinstall.citadel.org/install -O easyinstall.sh
chmod+x easyinstall.sh
edit the top line to
#!/bin/bash -x
run it and see what is happening..
You might be benefited by the other conversation also.
Perpetuating that hijacking was probably my fault.. I did edit the subject line when I replied, but yes it should have been a new thread.. My apology for that.
But.. You might both be having the same issue, (seems like a string/path thing..) and can benefit by working together to complete that section of easy install.
Subject: Re: BerkeleyDB lib error while installing with Easy Install
Check your syslog, maybe there are some clues as to why citserver did not start.
for you I think that is going to be /var/log/messages
grep -i citserver /var/log/messages
even
grep -i citadel /var/log/messages
even ../var/log/*
could be user/permission issue, or ports
Thu Jun 18 2020 10:12:55 AM EDT from easy now @ Uncensored Subject: Re: BerkeleyDB lib error while installing with Easy InstallOk. Thanks.
So far..
My script stayed alive after answering yes to letting it install dependencies. It went ahead and downloaded and install all including the elusive berkeleydb and webcit. But it aborted at the last huddle trying to connect to a running Citadel server.
Error: Setup could not connect to a running Citadel server.: No such file or directory /usr/local/citadel/citadel-admin.socket.
The question is 'am I missing something? should I attempt to start citadel and webcit even with this error? and would they start?
Tue Jun 16 2020 12:39:15 EDT from warbaby @ Uncensored Subject: Re: BerkeleyDB lib error while installing with Easy InstallI would run that from your home directory or ~/bin if you have a "bin" in your home directory and path.
if you run
wget http://easyinstall.citadel.org/installThe file name will be 'install' and will appear in the directory you ran the command from. pwd
If you run
wget http://easyinstall.citadel.org/install -O easyinstall.sh chmod +x easyinstall.shThat will help you identify the file later on, also so things like syntax highlighting work.
Tue Jun 16 2020 12:28:11 PM EDT from easy now @ Uncensored Subject: Re: BerkeleyDB lib error while installing with Easy Install
Thanks for your reply warbaby. I appreciate it.
So, I ran the "wget http://easyinstall.citadel.org/install...." from inside usr/local/ to download the easyinstall.sh but could find the file anywhere.
Where did wget save the easyinstall.sh file please?
Thanks
Mon Jun 15 2020 11:34:47 EDT from warbaby @ Uncensored Subject: Re: BerkeleyDB lib error while installing with Easy InstallI was talking strictly about easyinstall, the package retrieval for SUSE was left for another day.. I am not aware of packages for SUSE.. but that doesn't mean they don't exist.
try this..
wget http://easyinstall.citadel.org/install -O easyinstall.sh
chmod+x easyinstall.sh
edit the top line to
#!/bin/bash -x
run it and see what is happening..
You might be benefited by the other conversation also.
Perpetuating that hijacking was probably my fault.. I did edit the subject line when I replied, but yes it should have been a new thread.. My apology for that.
But.. You might both be having the same issue, (seems like a string/path thing..) and can benefit by working together to complete that section of easy install.
hi myself ketavmodi and i had installed citadel in centos 7 and firewall adn selinux is disabled by default but i need to know how to configure citadel to multi-domain
If I understand what you're asking, you want to log in to WebCit as the admin user, and go to
Administration > Domain Names and Internet Mail Configuration
then add your
a) Local host aliases
b) Masqueradable domains
This implies all your DNS is correctly configured.
Off the top of my head, not sure if this is a restart situation, although, I'd do at lease a citadel restart.. if not a soft reboot.
Then start sending test emails, and replying to them.
Fri Jun 19 2020 08:01:33 AM EDT from ketavmodi @ Uncensored Subject: how to configure multi domain
hi myself ketavmodi and i had installed citadel in centos 7 and firewall adn selinux is disabled by default but i need to know how to configure citadel to multi-domain
No, I had trace off but with trace on it looks like that:
checking sieve2.h usability... yes
checking sieve2.h presence... yes
checking for sieve2.h... yes
checking for sieve2_license in -lsieve... no
configure: error: libsieve was not found and is required. More info: http://www.citadel.org/doku.php/installation:start
+ die
+ show_alert Citadel Easy Install is aborting.
+ echo '' Citadel Easy Install is aborting. ''
Citadel Easy Install is aborting.
+ show_alert The last few lines above this message may indicate what went wrong.
+ echo '' The last few lines above this message may indicate what went wrong. ''
The last few lines above this message may indicate what went wrong.
+ show_alert Linux openSUSE 'NAME="openSUSE' 'Leap"' 'VERSION="15.1"' 'ID="opensuse-leap"' 'ID_LIKE="suse' 'opensuse"' 'VERSION_ID="15.1"' 'PRETTY_NAME="openSUSE' Leap '15.1"' 'ANSI_COLOR="0;32"' 'CPE_NAME="cpe:/o:opensuse:leap:15.1"' 'BUG_REPORT_URL="https://bugs.opensuse.org"' 'HOME_URL="https://www.opensuse.org/"' '(' 4.12.14-lp151.28.52-default 'x86_64)'
+ echo '' Linux openSUSE 'NAME="openSUSE' 'Leap"' 'VERSION="15.1"' 'ID="opensuse-leap"' 'ID_LIKE="suse' 'opensuse"' 'VERSION_ID="15.1"' 'PRETTY_NAME="openSUSE' Leap '15.1"' 'ANSI_COLOR="0;32"' 'CPE_NAME="cpe:/o:opensuse:leap:15.1"' 'BUG_REPORT_URL="https://bugs.opensuse.org"' 'HOME_URL="https://www.opensuse.org/"' '(' 4.12.14-lp151.28.52-default 'x86_64)' ''
Linux openSUSE NAME="openSUSE Leap" VERSION="15.1" ID="opensuse-leap" ID_LIKE="suse opensuse" VERSION_ID="15.1" PRETTY_NAME="openSUSE Leap 15.1" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:15.1" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" ( 4.12.14-lp151.28.52-default x86_64)
+ cd /root
+ rm -fr /tmp/citadel-build.13887
+ exit 1
a manual ./configure did run fine:
gerum:/tmp/citadel-build.8911/libsieve-2.2.7/src # ./configure --prefix=/usr/local/ctdlsupport
configure: loading site script /usr/share/site/x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for a BSD-compatible install... /usr/bin/install -c
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/x86_64-suse-linux/bin/ld
checking if the linker (/usr/x86_64-suse-linux/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/x86_64-suse-linux/bin/ld option to reload object files... -r
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... no
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for ANSI C header files... (cached) yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking for unistd.h... (cached) yes
checking alloca.h usability... yes
checking alloca.h presence... yes
checking for alloca.h... yes
checking for an ANSI C-conforming const... yes
checking for size_t... yes
checking whether byte ordering is bigendian... no
checking endian.h usability... yes
checking endian.h presence... yes
checking for endian.h... yes
checking for working memcmp... yes
checking for vprintf... yes
checking for _doprnt... no
configure: creating ./config.status
config.status: creating libsieve.pc
config.status: creating sv_parser/Makefile
config.status: creating sv_regex/Makefile
config.status: creating sv_interface/Makefile
config.status: creating sv_util/Makefile
config.status: creating sv_test/Makefile
config.status: creating sv_include/Makefile
config.status: creating Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
Wed Jun 17 2020 21:41:09 EDT from warbaby @ Uncensored Subject: Re: sieve2_license errorOkay, I had to find a recent build dir in /tmp..
So, here's the question..
did you run easyinstall with trace on (eg #!/bin/bash -x on first line),
and if so, what did your configure line look like? [it may be another double-quote situation..]
I did it manually, and it worked fine.
so try it.. (your build number will be different)..
then post your results..
[problem may not be here at all.. may be install options.]
root@ftp:/tmp/citadel-build.2704/libsieve-2.2.7/src# ./configure --prefix=/usr/local/ctdlsupport
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for a BSD-compatible install... /usr/bin/install -c
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/bin/ld option to reload object files... -r
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for ANSI C header files... (cached) yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking for unistd.h... (cached) yes
checking alloca.h usability... yes
checking alloca.h presence... yes
checking for alloca.h... yes
checking for an ANSI C-conforming const... yes
checking for size_t... yes
checking whether byte ordering is bigendian... no
checking endian.h usability... yes
checking endian.h presence... yes
checking for endian.h... yes
checking for working memcmp... yes
checking for vprintf... yes
checking for _doprnt... no
configure: creating ./config.status
config.status: creating libsieve.pc
config.status: creating sv_parser/Makefile
config.status: creating sv_regex/Makefile
config.status: creating sv_interface/Makefile
config.status: creating sv_util/Makefile
config.status: creating sv_test/Makefile
config.status: creating sv_include/Makefile
config.status: creating Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commandsWed Jun 17 2020 06:16:16 PM EDT from bgerum2 @ Uncensored Subject: Re: sieve2_license errorI forced the installation of libsieve by inserting OLDSUM=does_not_exist in line 445 in the installer.
it did install fine:
gmake[2]: Entering directory '/tmp/citadel-build.13687/libsieve-2.2.7/src/sv_include'
gmake[2]: Nothing to be done for 'install-exec-am'.
test -z "/usr/local/ctdlsupport/include" || /usr/bin/mkdir -p "/usr/local/ctdlsupport/include"
/usr/bin/install -c -m 644 'sieve2.h' '/usr/local/ctdlsupport/include/sieve2.h'
/usr/bin/install -c -m 644 'sieve2_error.h' '/usr/local/ctdlsupport/include/sieve2_error.h'
gmake[2]: Leaving directory '/tmp/citadel-build.13687/libsieve-2.2.7/src/sv_include'
gmake[1]: Leaving directory '/tmp/citadel-build.13687/libsieve-2.2.7/src/sv_include'
Complete.but now I'm back with the license error:
checking sieve2.h usability... yes
checking sieve2.h presence... yes
checking for sieve2.h... yes
checking for sieve2_license in -lsieve... no
configure: error: libsieve was not found and is required. More info: http://www.citadel.org/doku.php/installation:start
Citadel Easy Install is aborting.
Tue Jun 16 2020 11:13:54 EDT from warbaby @ Uncensored Subject: Re: sieve2_license errorYou're welcome Art.. It's my pleasure. to help out.
My last thought on this one at the moment should be in a new thread though..
The /tmp/citadel-install.log file.. easyinstall is not in the main repos that I can see.. so I couldn't check the git log for that.
I think the bash trace will help out. But, I distinctly recall that handy message from easy install
"something has failed.. you might look in /tmp/citadel-install.log" or something like that.
Mon Jun 15 2020 10:49:34 PM EDT from IGnatius T Foobar @ Uncensored Subject: Re: sieve2_license errorThank you warbaby for the excellent insight and help.
I will echo the request for our OpenSuSE friends to post the completed diffs to the Easy Install script to make it run properly on OpenSuSE. We will cheerfully accept any changes that are needed. It's just that we don't have anyone on the core team that uses this distribution so we don't normally test with it.
In the future we will have a Docker container for Citadel and I hope most people will use that.
Mon Jun 15 2020 05:21:10 PM EDT from warbaby @ Uncensored Subject: Re: sieve2_license errorI encourage you to keep cracking away at it. It's probably just a path.. You might need to add symlink. I have some other stuff todo for a while, but am still monitoring the thread.
Hi,
I have upgraded to Citadel 929 Easy Install from 917 installed from .debs, due to upgrading the server to Debian Buster.
Up until now I have been using the "hot" backup method with a script that issues /usr/local/citadel/sendcommand "CULL" after the backup is complete. However, after the upgrade the log files are no longer being deleted.
root@myserver:~# /usr/local/citadel/sendcommand "CULL"
sendcommand: started (pid=25745) connecting to Citadel server at /usr/local/citadel/citadel-admin.socket
200 helium Citadel server ADMIN CONNECTION ready.
CULL
530 Unrecognized or unsupported command.
Can I just delete logs older than a certain date instead? Or did "CULL" have some other effect too?
Thanks,
Ben