Error accessing Piler

Hi,

Today I needed to access Piler and got the following error:

Error: SQLSTATE[HY000] [2002] Connection refused on database: sphinx

Any ideas?

I searched the Piler logs and only found the following error:
2025-02-03T13:03:33Z [1:piler1:agent@piler1] Error: no container with name or ID “piler-app” found: no such container

It seems some contaiers are not running. Check the system load and search the logs for other errors.

Nethserver is installed on a proxmox VM.
I shut it down and added more memory.
I still have the same error.
In the proxmox VM Summary tha memory usage is at 52% and CPU usage is varying from 2.8% to 36.4%.
Her’s the log from Piler:

2025-02-03T15:48:40Z [1:piler1:systemd] Queued start job for default target Main User Target.
2025-02-03T15:48:40Z [1:piler1:systemd] Created slice User Application Slice.
2025-02-03T15:48:40Z [1:piler1:systemd] Started Mark boot as successful after the user session has run 2 minutes.
2025-02-03T15:48:40Z [1:piler1:systemd] Started Daily Cleanup of User’s Temporary Directories.
2025-02-03T15:48:40Z [1:piler1:systemd] Reached target Paths.
2025-02-03T15:48:40Z [1:piler1:systemd] Reached target Timers.
2025-02-03T15:48:40Z [1:piler1:systemd] Starting D-Bus User Message Bus Socket…
2025-02-03T15:48:40Z [1:piler1:systemd] Starting Create User’s Volatile Files and Directories…
2025-02-03T15:48:40Z [1:piler1:systemd] Listening on D-Bus User Message Bus Socket.
2025-02-03T15:48:40Z [1:piler1:systemd] Reached target Sockets.
2025-02-03T15:48:40Z [1:piler1:systemd] Finished Create User’s Volatile Files and Directories.
2025-02-03T15:48:40Z [1:piler1:systemd] Reached target Basic System.
2025-02-03T15:48:40Z [1:piler1:systemd] Started Rootless module/piler1 agent.
2025-02-03T15:48:40Z [1:piler1:systemd] Starting Podman piler.service…
2025-02-03T15:48:41Z [1:piler1:systemd] Starting D-Bus User Message Bus…
2025-02-03T15:48:41Z [1:piler1:dbus-broker-launch] Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
2025-02-03T15:48:41Z [1:piler1:dbus-broker-launch] Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
2025-02-03T15:48:41Z [1:piler1:systemd] Started D-Bus User Message Bus.
2025-02-03T15:48:41Z [1:piler1:] Ready
2025-02-03T15:48:41Z [1:piler1:systemd] Created slice Slice /user.
2025-02-03T15:48:41Z [1:piler1:systemd] Created slice cgroup user-libpod_pod_b4accded1e8659695d6f7e1cd8b7b562152c8fb9c399b2dd700d1227d277bdef.slice.
2025-02-03T15:48:41Z [1:piler1:podman] b4accded1e8659695d6f7e1cd8b7b562152c8fb9c399b2dd700d1227d277bdef
2025-02-03T15:48:41Z [1:piler1:systemd] podman-pause-93bfa0a3.scope: unit configures an IP firewall, but not running as root.
2025-02-03T15:48:41Z [1:piler1:systemd] (This warning is only shown for the first unit using IP firewalling.)
2025-02-03T15:48:41Z [1:piler1:systemd] Started podman-pause-93bfa0a3.scope.
2025-02-03T15:48:42Z [1:piler1:systemd] Started libcrun container.
2025-02-03T15:48:42Z [1:piler1:podman] piler
2025-02-03T15:48:42Z [1:piler1:systemd] Started Podman piler.service.
2025-02-03T15:48:42Z [1:piler1:systemd] Reached target Main User Target.
2025-02-03T15:48:42Z [1:piler1:systemd] Starting Podman mariadb-app.service…
2025-02-03T15:48:42Z [1:piler1:systemd] Starting Podman memcached-app.service…
2025-02-03T15:48:44Z [1:piler1:systemd] Started libcrun container.
2025-02-03T15:48:44Z [1:piler1:piler1] 7c02166a2d09d1773685e80fe39d04ff6feccda2308886a92a4a253683038221
2025-02-03T15:48:44Z [1:piler1:systemd] Started libcrun container.
2025-02-03T15:48:44Z [1:piler1:systemd] Started Podman memcached-app.service.
2025-02-03T15:48:44Z [1:piler1:piler1] b68f4456b01b66128fe215b10b79436b1601eed6c9b6b7a03bc35889bf9ac74a
2025-02-03T15:48:45Z [1:piler1:mariadb-app] 2025-02-03 15:48:45+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.11.7+maria~ubu2204 started.
2025-02-03T15:48:47Z [1:piler1:systemd] Started Podman mariadb-app.service.
2025-02-03T15:48:47Z [1:piler1:systemd] Starting Podman piler-app.service…
2025-02-03T15:48:48Z [1:piler1:mariadb-app] 2025-02-03 15:48:48+00:00 [Warn] [Entrypoint]: /sys/fs/cgroup///memory.pressure not writable, functionality unavailable to MariaDB
2025-02-03T15:48:48Z [1:piler1:mariadb-app] 2025-02-03 15:48:48+00:00 [Note] [Entrypoint]: Switching to dedicated user ‘mysql’
2025-02-03T15:48:48Z [1:piler1:mariadb-app] 2025-02-03 15:48:48+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.11.7+maria~ubu2204 started.
2025-02-03T15:48:50Z [1:piler1:mariadb-app] 2025-02-03 15:48:50+00:00 [Note] [Entrypoint]: MariaDB upgrade not required
2025-02-03T15:48:50Z [1:piler1:mariadb-app] 2025-02-03 15:48:50 0 [Note] Starting MariaDB 10.11.7-MariaDB-1:10.11.7+maria~ubu2204 source revision 87e13722a95af5d9378d990caf48cb6874439347 as process 1
2025-02-03T15:48:50Z [1:piler1:mariadb-app] 2025-02-03 15:48:50 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2025-02-03T15:48:50Z [1:piler1:mariadb-app] 2025-02-03 15:48:50 0 [Note] InnoDB: Number of transaction pools: 1
2025-02-03T15:48:50Z [1:piler1:mariadb-app] 2025-02-03 15:48:50 0 [Note] InnoDB: Using SSE4.2 crc32 instructions
2025-02-03T15:48:50Z [1:piler1:mariadb-app] 2025-02-03 15:48:50 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
2025-02-03T15:48:50Z [1:piler1:mariadb-app] 2025-02-03 15:48:50 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2025-02-03T15:48:51Z [1:piler1:mariadb-app] 2025-02-03 15:48:51 0 [Note] InnoDB: Completed initialization of buffer pool
2025-02-03T15:48:51Z [1:piler1:mariadb-app] 2025-02-03 15:48:51 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)
2025-02-03T15:48:51Z [1:piler1:mariadb-app] 2025-02-03 15:48:51 0 [Note] InnoDB: End of log at LSN=51270396
2025-02-03T15:48:52Z [1:piler1:mariadb-app] 2025-02-03 15:48:52 0 [Note] InnoDB: 128 rollback segments are active.
2025-02-03T15:48:52Z [1:piler1:mariadb-app] 2025-02-03 15:48:52 0 [Note] InnoDB: Setting file ‘./ibtmp1’ size to 12.000MiB. Physically writing the file full; Please wait …
2025-02-03T15:48:52Z [1:piler1:mariadb-app] 2025-02-03 15:48:52 0 [Note] InnoDB: File ‘./ibtmp1’ size is now 12.000MiB.
2025-02-03T15:48:52Z [1:piler1:mariadb-app] 2025-02-03 15:48:52 0 [Note] InnoDB: log sequence number 51270396; transaction id 66626
2025-02-03T15:48:52Z [1:piler1:mariadb-app] 2025-02-03 15:48:52 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2025-02-03T15:48:52Z [1:piler1:mariadb-app] 2025-02-03 15:48:52 0 [Note] Plugin ‘FEEDBACK’ is disabled.
2025-02-03T15:48:52Z [1:piler1:mariadb-app] 2025-02-03 15:48:52 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
2025-02-03T15:48:52Z [1:piler1:mariadb-app] 2025-02-03 15:48:52 0 [Note] Server socket created on IP: ‘0.0.0.0’.
2025-02-03T15:48:52Z [1:piler1:mariadb-app] 2025-02-03 15:48:52 0 [Note] Server socket created on IP: ‘::’.
2025-02-03T15:48:52Z [1:piler1:mariadb-app] 2025-02-03 15:48:52 0 [Note] InnoDB: Buffer pool(s) load completed at 250203 15:48:52
2025-02-03T15:48:52Z [1:piler1:mariadb-app] 2025-02-03 15:48:52 0 [Note] mariadbd: ready for connections.
2025-02-03T15:48:52Z [1:piler1:mariadb-app] Version: ‘10.11.7-MariaDB-1:10.11.7+maria~ubu2204’ socket: ‘/run/mysqld/mysqld.sock’ port: 3306 mariadb.org binary distribution
2025-02-03T15:48:58Z [1:piler1:systemd] Started libcrun container.
2025-02-03T15:48:58Z [1:piler1:piler1] fb0f1196504035ef60e10e4d84782961a6baf7c51ee2c9aabc48c6e7bc735c5e
2025-02-03T15:48:58Z [1:piler1:systemd] Started Podman piler-app.service.
2025-02-03T15:48:58Z [1:piler1:systemd] Startup finished in 18.776s.
2025-02-03T15:48:59Z [1:piler1:piler-app] Database
2025-02-03T15:48:59Z [1:piler1:piler-app] information_schema
2025-02-03T15:48:59Z [1:piler1:piler-app] piler
2025-02-03T15:48:59Z [1:piler1:piler-app] DEBUG: 127.0.0.1 is ready
2025-02-03T15:48:59Z [1:piler1:piler-app] DEBUG: metadata table exists
2025-02-03T15:48:59Z [1:piler1:piler-app] * Starting periodic command scheduler cron
2025-02-03T15:48:59Z [1:piler1:piler-app] …done.
2025-02-03T15:49:00Z [1:piler1:piler-app] * Starting nginx nginx
2025-02-03T15:49:01Z [1:piler1:piler-app] …done.
2025-02-03T15:49:01Z [1:piler1:piler-app] starting searchd . . .
2025-02-03T15:49:01Z [1:piler1:piler-app] [Mon Feb 3 15:49:01.742 2025] [52] using config file ‘/etc/piler/manticore.conf’ (10595 chars)…
2025-02-03T15:49:01Z [1:piler1:piler-app] Manticore 6.2.12 dc5144d35@230822 (columnar 2.2.4 5aec342@230822) (secondary 2.2.4 5aec342@230822)
2025-02-03T15:49:01Z [1:piler1:piler-app] Copyright (c) 2001-2016, Andrew Aksyonoff
2025-02-03T15:49:01Z [1:piler1:piler-app] Copyright (c) 2008-2016, Sphinx Technologies Inc (http://sphinxsearch.com)
2025-02-03T15:49:01Z [1:piler1:piler-app] Copyright (c) 2017-2023, Manticore Software LTD (https://manticoresearch.com)
2025-02-03T15:49:01Z [1:piler1:piler-app]
2025-02-03T15:49:01Z [1:piler1:piler-app] starting daemon version ‘6.2.12 dc5144d35@230822 (columnar 2.2.4 5aec342@230822) (secondary 2.2.4 5aec342@230822)’ …
2025-02-03T15:49:01Z [1:piler1:piler-app] listening on 127.0.0.1:9312 for sphinx and http(s)
2025-02-03T15:49:01Z [1:piler1:piler-app] listening on 127.0.0.1:9306 for mysql
2025-02-03T15:49:01Z [1:piler1:piler-app] Manticore 6.2.12 dc5144d35@230822 (columnar 2.2.4 5aec342@230822) (secondary 2.2.4 5aec342@230822)
2025-02-03T15:49:01Z [1:piler1:piler-app] Copyright (c) 2001-2016, Andrew Aksyonoff
2025-02-03T15:49:01Z [1:piler1:piler-app] Copyright (c) 2008-2016, Sphinx Technologies Inc (http://sphinxsearch.com)
2025-02-03T15:49:01Z [1:piler1:piler-app] Copyright (c) 2017-2023, Manticore Software LTD (https://manticoresearch.com)
2025-02-03T15:49:01Z [1:piler1:piler-app]
2025-02-03T15:49:01Z [1:piler1:piler-app] precaching table ‘main1’
2025-02-03T15:49:01Z [1:piler1:piler-app] precaching table ‘main2’
2025-02-03T15:49:01Z [1:piler1:piler-app] precaching table ‘main3’
2025-02-03T15:49:01Z [1:piler1:piler-app] precaching table ‘main4’
2025-02-03T15:49:01Z [1:piler1:piler-app] precaching table ‘dailydelta1’
2025-02-03T15:49:01Z [1:piler1:piler-app] rotating table ‘dailydelta1’: success
2025-02-03T15:49:01Z [1:piler1:piler-app] precaching table ‘delta1’
2025-02-03T15:49:02Z [1:piler1:piler-app] rotating table ‘delta1’: success
2025-02-03T15:49:02Z [1:piler1:piler-app] precaching table ‘tag1’
2025-02-03T15:49:02Z [1:piler1:piler-app] rotating table ‘tag1’: success
2025-02-03T15:49:02Z [1:piler1:piler-app] precaching table ‘note1’
2025-02-03T15:49:02Z [1:piler1:piler-app] rotating table ‘note1’: success
2025-02-03T15:49:02Z [1:piler1:piler-app] Manticore 6.2.12 dc5144d35@230822 (columnar 2.2.4 5aec342@230822) (secondary 2.2.4 5aec342@230822)
2025-02-03T15:49:02Z [1:piler1:piler-app] Copyright (c) 2001-2016, Andrew Aksyonoff
2025-02-03T15:49:02Z [1:piler1:piler-app] Copyright (c) 2008-2016, Sphinx Technologies Inc (http://sphinxsearch.com)
2025-02-03T15:49:02Z [1:piler1:piler-app] Copyright (c) 2017-2023, Manticore Software LTD (https://manticoresearch.com)
2025-02-03T15:49:02Z [1:piler1:piler-app]
2025-02-03T15:49:02Z [1:piler1:piler-app] starting piler-smtp . . .
2025-02-03T15:49:02Z [1:piler1:piler-app] starting piler . . .
2025-02-03T15:50:21Z [1:piler1:agent@piler1] task/module/piler1/c889a593-daf6-4477-868e-fb950e0c36bc: get-name/50get_name is starting
2025-02-03T15:50:21Z [1:piler1:agent@piler1] task/module/piler1/56b27ef5-b7a0-41ed-b8db-611d365a46f7: get-configuration/20read is starting
2025-02-03T15:50:21Z [1:piler1:agent@piler1] task/module/piler1/c82c644c-e05b-40db-a144-62d5cccde65b: get-status/20read is starting
2025-02-03T15:50:21Z [1:piler1:agent@piler1] task/module/piler1/c889a593-daf6-4477-868e-fb950e0c36bc: action “get-name” status is “completed” (0) at step 50get_name
2025-02-03T15:50:22Z [1:piler1:agent@piler1] task/module/piler1/c82c644c-e05b-40db-a144-62d5cccde65b: action “get-status” status is “completed” (0) at step validate-output.json
2025-02-03T15:50:22Z [1:piler1:agent@piler1] task/module/piler1/56b27ef5-b7a0-41ed-b8db-611d365a46f7: action “get-configuration” status is “completed” (0) at step validate-output.json
2025-02-03T15:50:43Z [1:piler1:systemd] Starting Mark boot as successful…
2025-02-03T15:50:43Z [1:piler1:systemd] Finished Mark boot as successful.
2025-02-03T15:53:43Z [1:piler1:systemd] Created slice User Background Tasks Slice.
2025-02-03T15:53:43Z [1:piler1:systemd] Starting Cleanup of User’s Temporary Files and Directories…
2025-02-03T15:53:43Z [1:piler1:systemd] Finished Cleanup of User’s Temporary Files and Directories.
2025-02-03T15:54:53Z [1:piler1:agent@piler1] task/module/piler1/fd6b987f-5f0c-4063-8144-f7b45e8a47e2: get-name/50get_name is starting
2025-02-03T15:54:53Z [1:piler1:agent@piler1] task/module/piler1/2bf7dce8-1848-42cd-bf6e-f7b33602df84: get-configuration/20read is starting
2025-02-03T15:54:53Z [1:piler1:agent@piler1] task/module/piler1/599b592f-ce13-445a-a731-fad0c9afd185: get-status/20read is starting
2025-02-03T15:54:54Z [1:piler1:agent@piler1] task/module/piler1/fd6b987f-5f0c-4063-8144-f7b45e8a47e2: action “get-name” status is “completed” (0) at step 50get_name
2025-02-03T15:54:54Z [1:piler1:agent@piler1] task/module/piler1/599b592f-ce13-445a-a731-fad0c9afd185: action “get-status” status is “completed” (0) at step validate-output.json
2025-02-03T15:54:54Z [1:piler1:agent@piler1] task/module/piler1/2bf7dce8-1848-42cd-bf6e-f7b33602df84: action “get-configuration” status is “completed” (0) at step validate-output.json Blockquote

Thank’s

Hi @Tiago

Is this system running on harddisks or SSDs inside of Proxmox?

You will need SSDs!

My 2 cents
Andy

Hi, While I admit that I’m not using SSDs, I only have 5 users.
I restored a backup from January 30 (before updated Mail app to 1.5.2) to a new VM and Piler is working.

Well then, you can expect problems every so often… Updates are often enough.

I also had to learn the hard way that almost ALL dev work was done with super fast new notebooks, all-NVMe…
A harddisk will often hit “Timeout” issues, even a SSD under Proxmox can be a little too slow, unless using “Enterprise Class” SSDs.

My Home- / Test-Proxmox, a small, low powered Odroid H3+ with 4 cores and 64 GB RAM is now ALL NVMe - and has no such issues anymore.

Even for 5 Users, I would strongly suggest to change!
I am a single user at home, and I had to change…

My 2 cents
Andy