PIler 1.0.0 configuration issues

Support
1

Installed it via software center and cofigured it with FQDN and mailserver and default retention days.

Created symlink /home/piler1/.config/systemd/user/default.target.wants/piler.service → /home/piler1/.config/systemd/user/piler.service.
Error: no container with name or ID "piler-app" found: no such container
Error: no container with name or ID "piler-app" found: no such container
Assertion failed
  File "/home/piler1/.config/actions/configure-module/90add-relay-rule", line 42, in <module>
    agent.assert_exp(response['exit_code'] == 0)

image
image1876×1450 175 KB

image
image1534×848 67.5 KB

image
image1328×922 15.4 KB

In settings the chosen mail domain is gone. It can beselected again, but the save button will stay grayed out.

HTH

2

cannot reproduce

image
image1009×915 40.8 KB

Does the mailserver was configured (first domain set)

3

well if the server is not configured we cannot save the form (it is expected)

image
image1009×915 29 KB

4

Yes, there is 1 mail domain configured up and running

5

When I select the one and only mail domain from the drop down, the save button stays greyed out.

6

What browser and version are you using?

7

Chrome
image

8

The first boot is quite long , we have a countdown of 60 seconds and maybe you hit it so you got a miconfigured instance

With my server I recall to wait 15 seconds…

Can you try again and check the time to install…the log could be also a clue because we print the time after each seconds IIRC

Anyway we need the log to understand

After the installation

journalctl > dump

9
  • Removed instance 1
  • Reinstalled instance 2
  • Waited until last log entry appeared in the log (see below), and waited 30 secs extra
  • Went to software center, instance, "not configured’ → configure
  • Enter FQDN, certificate and https, retention default
  • Same issue
  • Waited another 120 secs and tried to save again
  • Same issue
Created symlink /home/piler2/.config/systemd/user/default.target.wants/piler.service → /home/piler2/.config/systemd/user/piler.service.
Error: no container with name or ID "piler-app" found: no such container
Error: no container with name or ID "piler-app" found: no such container
Assertion failed
  File "/home/piler2/.config/actions/configure-module/90add-relay-rule", line 42, in <module>
    agent.assert_exp(response['exit_code'] == 0)
Copy to clipboard
Show less


2024-06-01T10:54:30+02:00 [1:piler2:agent@piler2] Writing manifest to image destination
2024-06-01T10:54:30+02:00 [1:piler2:agent@piler2] 9200bd86da810533901767e7211ee0accd4d5a762792e6f4d7bff4c5210eb910
2024-06-01T10:54:30+02:00 [1:piler2:agent@piler2] Trying to pull docker.io/library/memcached:1.6.26-alpine...
2024-06-01T10:54:32+02:00 [1:piler2:agent@piler2] Getting image source signatures
2024-06-01T10:54:32+02:00 [1:piler2:agent@piler2] Copying blob sha256:3d2a65ada68aba9def3ee64975e1d20608c30fbb31babe05bf0a052fd5b9e631
2024-06-01T10:54:32+02:00 [1:piler2:agent@piler2] Copying blob sha256:bf4ca62cc3e912d97d5818cdb2c21bfd6ef17fb2a46bb9ff37ef80b46aeb7579
2024-06-01T10:54:32+02:00 [1:piler2:agent@piler2] Copying blob sha256:8b997d515984ace5a566abec5f367a569bf51dcb5c860f5f1868154d8d61ca54
2024-06-01T10:54:32+02:00 [1:piler2:agent@piler2] Copying blob sha256:873fcbe9681f30840a11a64dc6ef9dfef47f40b1181e1c876969a13e35b6f5b4
2024-06-01T10:54:32+02:00 [1:piler2:agent@piler2] Copying blob sha256:7e9ac090217572c7ea3a76702db6866b9c0c35dd85d2a2bad5a50ca438050b67
2024-06-01T10:54:32+02:00 [1:piler2:agent@piler2] Copying blob sha256:4abcf20661432fb2d719aaf90656f55c287f8ca915dc1c92ec14ff61e67fbaf8
2024-06-01T10:54:32+02:00 [1:piler2:agent@piler2] Copying config sha256:b686fb4e394c572a1980b134344b94d4673fcf49dd492838d7ee6a22c4c73466
2024-06-01T10:54:32+02:00 [1:piler2:agent@piler2] Writing manifest to image destination
2024-06-01T10:54:33+02:00 [1:piler2:agent@piler2] b686fb4e394c572a1980b134344b94d4673fcf49dd492838d7ee6a22c4c73466
2024-06-01T10:54:33+02:00 [1:piler2:agent@piler2] task/module/piler2/33de0342-5cbb-4a0e-ba3d-249d4207e4d1: create-module/10selfadm_role is starting
2024-06-01T10:54:33+02:00 [1:piler2:agent@piler2] 1
2024-06-01T10:54:33+02:00 [1:piler2:agent@piler2] task/module/piler2/33de0342-5cbb-4a0e-ba3d-249d4207e4d1: create-module/10set_env is starting
2024-06-01T10:54:33+02:00 [1:piler2:agent@piler2] task/module/piler2/33de0342-5cbb-4a0e-ba3d-249d4207e4d1: action "create-module" status is "completed" (0) at step 10set_env
2024-06-01T10:56:36+02:00 [1:piler2:systemd] Starting Mark boot as successful...
2024-06-01T10:56:36+02:00 [1:piler2:systemd] Finished Mark boot as successful.

After second configure attempt https://pastebin.com/hTfG0YCf

ps. Maybe not related but I do not have the option relay configured in the mail module. Never touched it.

10

Is Mail updated to version 1.4.0+?

11

image

1 Like
12

You have the testing switch enabled. Is it wanted? Testing releases have more bugs than you expect :wink:

Apart from warning you for the testing switch, the Mail version is good.

1 Like
13

Nope, not at all, but living on the digital edge brings out the unexpected in an early stage :slight_smile: This is not a prod node