The workaround described above works. Changed it to following line and added few more system-users spotted in the AAA daemon logs:
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Oct 14 2024
Oct 12 2024
Oct 11 2024
Oct 10 2024
Oct 8 2024
Can you check if changing this line https://github.com/vyos/vyos-1x/blob/current/data/templates/login/tacplus_nss.conf.j2#L33 and adding those user helps?
This file can be changed locally in the router: /usr/share/vyos/templates/login/tacplus_nss.conf.j2
Change line:
exclude_users=root,telegraf,radvd,strongswan,tftp,conservr,frr,ocserv,pdns,_chrony,_lldpd,sshd,openvpn,radius_user,radius_priv_user,*{{ ',' + user | join(',') if user is vyos_defined }}And change it to something like:
Oct 6 2024
Oct 4 2024
Oct 3 2024
Oct 2 2024
Oct 1 2024
I think this will not be required
Sep 29 2024
Sep 28 2024
Sep 25 2024
Also probably related:
I would expect the line of CLI being used to be in any of these files?
Sep 24 2024
Sep 22 2024
Sep 21 2024
Sep 18 2024
I think, a new command is required for this show integrity or similar. Also a brief status in MOTD and show version.
Do you want some CLI for it? Or just user util?
Sep 17 2024
Sep 16 2024
Sep 15 2024
Sep 9 2024
Sep 2 2024
Aug 31 2024
Aug 30 2024
Aug 26 2024
Aug 23 2024
Only worked:
- Reboot instance
- load /config/config.boot
- sudo podman rm suricata
- commit
Then it works
vyos@VyOS-Test01#
[edit]
vyos@VyOS-Test01# load /config/config.boot
[edit]
vyos@VyOS-Test01#
[edit]
vyos@VyOS-Test01# compare
+ container {
+ name suricata {
+ allow-host-networks
+ arguments "-q 1"
+ capability "net-admin"
+ capability "sys-admin"
+ capability "sys-nice"
+ image "jasonish/suricata:6.0.14"
+ memory "1024"
+ volume ETC {
+ destination "/etc/suricata"
+ source "/config/suricata/etc"
+ }
+ volume LOGS {
+ destination "/var/log/suricata"
+ source "/config/suricata/logs"
+ }
+ volume RULES {
+ destination "/var/lib/suricata/rules/"
+ source "/config/suricata/rules"
+ }
+ }
+ }If service is 'failed' state
vyos@VyOS-Test01:~$ systemctl status vyos-container-suricata.service
× vyos-container-suricata.service - VyOS Container suricata
Loaded: loaded (/run/systemd/system/vyos-container-suricata.service; static)
Active: failed (Result: exit-code) since Fri 2024-08-23 10:32:44 UTC; 43s ago
Duration: 4min 55.702s
Process: 2855 ExecStartPre=/bin/rm -f /run/vyos-container-suricata.service.pid /run/vyos-container-suricata.service.cid (code=exited, sta>
Process: 2856 ExecStart=/usr/bin/podman run --conmon-pidfile /run/vyos-container-suricata.service.pid --cidfile /run/vyos-container-suric>
Process: 2867 ExecStopPost=/usr/bin/podman rm --ignore -f --cidfile /run/vyos-container-suricata.service.cid (code=exited, status=0/SUCCE>
Process: 2873 ExecStopPost=/bin/rm -f /run/vyos-container-suricata.service.cid (code=exited, status=0/SUCCESS)
CPU: 129msIn T6673#198344, @a.hajiyev wrote:You are right there is an op-mode command to restart the container
restart container suricataBut I think there needs to be some checks/changes at least someone will execute the native Podman command to restart the container.
You are right there is an op-mode command to restart the container
restart container suricata
But I think there needs to be some checks/changes at least someone will execute the native Podman command to restart the container.
It fails because you do it in the wrong way