Re: FreeBSD webadmin "connect: No such file or directory" - socket/path issue

Harry Duncan <[email protected]> Sun, 21 Dec 2025 13:42:53 +0000
Newsgroups gmane.mail.imap.courier.general
Message-ID <CAHAPYVA48Ws=rZidw-hMNBHULXCrQHcoKFSpm8GC-qOEcJcigA@mail.gmail.com>
--===============3632256019415548022==
Content-Type: multipart/alternative; boundary="000000000000cb3d980646767cd1"

--000000000000cb3d980646767cd1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sunday, December 21, 2025, Sam Varshavchik <[email protected]> wrote=
:

> Harry Duncan writes:
>>
>> I expected the deployement path to be easier and quicker than building
>> from sources, but it hasn't, probably because I spent a lot of time doin=
g
>> diff on config files etc.
>>
>
> One trick, for this sort of a thing, is to just copy the existing
> configuration files into the to-be-installed, pre-created directory, and
> then install the package.


> Assuming that the package follows the instructions in INSTALL, sysconftoo=
l
> will run during installation. It will remove individual obsoleted
> configuration settings, preserve the unchanged configuration settings, an=
d
> configuration settings that are not backward-compatible get reset to thei=
r
> new defaults.


That is really good to know

>
>>
>> I resolved sqwebmail running when I identified that it was expecting its
>> socket at /var/sqerbmail/sqerbmail.sock but the package created it at
>> /var/spool/courier/sqwebmail.sock
>>
>
> This sounds like you were trying to ended up with a combination of both
> the standalone sqwebmail package and the webmail subpackage of Courier.
> This looks like a packaging error.


The main courier package on freebsd didn=E2=80=99t appear to install sqwebm=
ail at
all, had to use a standalone package. Wasn=E2=80=99t my expectation either =
.

Had a similar thing with authdaemon, no backends were installed and had to
be installed by a separate package. Again, not my expectation but ok.


>
> There was nothing deployed to /var/spool/courier/webadmin by the package
>>
>
> That's where the socket lives.
>
> the question therefore is: What should /var/spool/courier/webadmin
>> actually be?
>>
>
> Nothing. webadmin will create it, when it is started for real.
>
> On the old linux server there is no webadmin daemon running (ps / lsof
>> show nothing)
>>
>
> There should be. I do not recall if in ancient times webadmin was just a
> perl script, what's now webadmin.pl, and there was a separate suid
> wrapper for actually installing the updated configuration files.


Yeah, it was different :-( and I assumed I knew what I was doing


>
> is
>   a three step process:
>
>    1. Move /usr/lib/courier/libexec/courier/webmail/webadmin to your web
>       server's SSL cgi-bin directory.
>
>    2. Add the following command to your system startup script:
>
> /var/www/cgi-bin/webadmin daemon &
>
> Many packages, including my rpm packages, just install a symlink in the
> cgi-bin directory instead of putting the binary there, but what you appea=
r
> to be missing is the step of starting webadmin, as per the above, as root=
.


Excellent, it=E2=80=99s not fully running but it is running at least. Bombi=
ng out
on line 6 of the Perl script.

I=E2=80=99ve a manual to read! Get updated.

Thanks do e your prompt response, it is really appreciated

Harry

--000000000000cb3d980646767cd1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<br><br>On Sunday, December 21, 2025, Sam Varshavchik &lt;<a href=3D"mailto=
:[email protected]">[email protected]</a>&gt; wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">Harry Duncan writes:<blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I expected the deployement path to be easier and quicker than building from=
 sources, but it hasn&#39;t, probably because I spent a lot of time doing d=
iff on config files etc.<br>
</blockquote>
<br>
One trick, for this sort of a thing, is to just copy the existing configura=
tion files into the to-be-installed, pre-created directory, and then instal=
l the package.</blockquote><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Assuming that the package follows the instructions in INSTALL, sysconftool =
will run during installation. It will remove individual obsoleted configura=
tion settings, preserve the unchanged configuration settings, and configura=
tion settings that are not backward-compatible get reset to their new defau=
lts.</blockquote><div><br></div><div>That is really good to know=C2=A0</div=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex"><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
I resolved sqwebmail running when I identified that it was expecting its so=
cket at /var/sqerbmail/sqerbmail.sock but the package created it at /var/sp=
ool/courier/sqwebmail.s<wbr>ock<br>
</blockquote>
<br>
This sounds like you were trying to ended up with a combination of both the=
 standalone sqwebmail package and the webmail subpackage of Courier. This l=
ooks like a packaging error.</blockquote><div><br></div><div>The main couri=
er package on freebsd didn=E2=80=99t appear to install sqwebmail at all, ha=
d to use a standalone package. Wasn=E2=80=99t my expectation either .</div>=
<div><br></div><div>Had a similar thing with authdaemon, no backends were i=
nstalled and had to be installed by a separate package. Again, not my expec=
tation but ok.=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">There was nothing deployed to /var/spool/cou=
rier/webadmin by the package<br>
</blockquote>
<br>
That&#39;s where the socket lives.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
the question therefore is: What should /var/spool/courier/webadmin actually=
 be?<br>
</blockquote>
<br>
Nothing. webadmin will create it, when it is started for real.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On the old linux server there is no webadmin daemon running (ps / lsof show=
 nothing)<br>
</blockquote>
<br>
There should be. I do not recall if in ancient times webadmin was just a pe=
rl script, what&#39;s now <a href=3D"http://webadmin.pl" target=3D"_blank">=
webadmin.pl</a>, and there was a separate suid wrapper for actually install=
ing the updated configuration files.</blockquote><div><br></div><div>Yeah, =
it was different :-( and I assumed I knew what I was doing</div><div>=C2=A0=
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">
<br>is<br>
=C2=A0 a three step process:<br>
<br>
=C2=A0 =C2=A01.=C2=A0Move /usr/lib/courier/libexec/couri<wbr>er/webmail/web=
admin to your web<br>
=C2=A0 =C2=A0 =C2=A0 server&#39;s SSL cgi-bin directory.<br>
<br>
=C2=A0 =C2=A02.=C2=A0Add the following command to your system startup scrip=
t:<br>
<br>
/var/www/cgi-bin/webadmin daemon &amp;<br>
<br>
Many packages, including my rpm packages, just install a symlink in the cgi=
-bin directory instead of putting the binary there, but what you appear to =
be missing is the step of starting webadmin, as per the above, as root.</bl=
ockquote><div><br></div><div>Excellent, it=E2=80=99s not fully running but =
it is running at least. Bombing out on line 6 of the Perl script.</div><div=
><br></div><div>I=E2=80=99ve a manual to read! Get updated.</div><div><br><=
/div><div>Thanks do e your prompt response, it is really appreciated=C2=A0<=
/div><div><br></div><div>Harry</div>

--000000000000cb3d980646767cd1--


--===============3632256019415548022==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============3632256019415548022==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

--===============3632256019415548022==--