Re: Problem getting spider to start

null@example.com (ZhangHuangbin) — Sun, 25 Jun 2023 07:46:10 +0000

Hi Alan,

Do you still have issue with Spider?
We just released v2.4.0 today, you may want to give it a try.
https://spiderd.io/

Re: Problem getting spider to start

null@example.com (AlanHarwood) — Tue, 20 Jun 2023 09:59:36 +0000

ZhangHuangbin wrote:

Any error in /opt/spider/log/*.log?

Only warnings of invalid archiving addresses and info of anonymous connections.

Re: Problem getting spider to start

null@example.com (AlanHarwood) — Tue, 20 Jun 2023 09:53:41 +0000

I think I have realised what I did wrong.
Only when I noticed that my mail system was down did I realise that spider and postfix were not on speaking terms, and that nginx was preventing spider's web service from running. Once I stopped postfix and nginx and reinstalled spider, I could then access the web interface on :8080.
I should have worked this out yesterday, it was obvious after a good night's sleep.

Re: Problem getting spider to start

null@example.com (ZhangHuangbin) — Tue, 20 Jun 2023 00:02:50 +0000

Any error in /opt/spider/log/*.log?

Problem getting spider to start

null@example.com (AlanHarwood) — Mon, 19 Jun 2023 16:39:08 +0000

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release):
- Deployed with iRedMail Easy or the downloadable installer?
- Linux/BSD distribution name and version:
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Web server (Apache or Nginx):
- Manage mail accounts with iRedAdmin-Pro?
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====
iRedMail 1.6.3 MARIADB edition deployed with Easy.
Ubuntu 22.04.2 LTS (GNU/Linux 5.15.0-75-generic x86_64)
Backend MariaDB
Webserver Nginx
not pro iRedAdmin

But I don't think much of the above is relevant apart from Ubuntu details.
I am trying to install spider.

I downloaded spider-v2.3.0 extracted the tar and ran the install.
Installation appeared to work and auto-started, but then stopped with error message:

Process: 66505 ExecStart=/usr/local/bin/spiderd (code=exited, status=255/EXCEPTION)

It then auto-restarts and produces the same error.

A manual start produces the following message:

**************************************************************
******************** ERROR *************************
**************************************************************
Failed to start the service, please check console output
and log file (/var/log/messages or /var/log/syslog), contact
support if necessary: {link to spider removed}

The log files don't help me, just giving the entries:

Jun 19 16:39:48 mail systemd[1]: /lib/systemd/system/spiderd.service:20: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.

and

Jun 19 16:39:48 mail systemd[321535]: spiderd.service: Failed to determine user credentials: No such process
Jun 19 16:39:48 mail systemd[321535]: spiderd.service: Failed at step USER spawning /usr/local/bin/spiderd: No such process
Jun 19 16:39:48 mail systemd[1]: spiderd.service: Main process exited, code=exited, status=217/USER
Jun 19 16:39:48 mail systemd[1]: spiderd.service: Failed with result 'exit-code'.

I did not know what to do, so I repeated the whole procedure on another server with the same versions of iRedMail, Ubuntu and spider, and, no surprise, got exactly the same results.

What am I doing wrong?

iRedMail — Problem getting spider to start

Re: Problem getting spider to start

Re: Problem getting spider to start

Re: Problem getting spider to start

Re: Problem getting spider to start

Problem getting spider to start