This script runs fine in the console, but fails to start the container in cron. So, lxc-stop will work fine in cron, but lxc-start won't
The cron message I receive is lxc-start wait_on_daemonized_start: 833 No such file or directory - Failed to receive the container state
for CONTAINER in $(lxc-ls -1 | grep data); do
lxc-stop --name=$CONTAINER
sleep 2
lxc-start --daemon --name=$CONTAINER
done
Any idea why it is only start that is failing in cron?
It is a Debian 9 container running on a Debian 9 host.
Every now and then the container would grind to a halt. It is usually a slow task like apticron or munin. My last test was an idle container on an idle server, and the same thin happened again. Over 300 Cron processes.
The host copes with all these tasks and more, it is just inside a container that these problems start.
Any tips or suggestions? Thanks
root 816 0.0 0.0 54812 3860 ? Ss Aug28 0:00 [lxcmonitor] /srv/lxc test-01
root 908 0.0 0.0 28236 4428 ? Ss Aug28 0:00 \_ /sbin/init
root 1266 0.0 0.0 32968 3956 ? Ss Aug28 0:00 \_ /lib/systemd/systemd-journald
root 1445 0.0 0.0 37080 2700 ? Ss Aug28 0:00 \_ /sbin/rpcbind -w
statd 1466 0.0 0.0 37280 2908 ? Ss Aug28 0:00 \_ /sbin/rpc.statd
root 1491 0.0 0.0 27568 228 ? Ss Aug28 0:00 \_ /usr/sbin/rpc.idmapd
root 1496 0.0 0.0 27504 2768 ? Ss Aug28 0:00 \_ /usr/sbin/cron -f
root 9455 0.0 0.0 52788 2800 ? S Aug28 0:00 | \_ /usr/sbin/CRON -f
root 10293 0.0 0.0 52788 2800 ? S Aug28 0:00 | \_ /usr/sbin/CRON -f
root 11147 0.0 0.0 52788 2800 ? S Aug28 0:00 | \_ /usr/sbin/CRON -f
root 12047 0.0 0.0 52788 2800 ? S Aug28 0:00 | \_ /usr/sbin/CRON -f
root 12881 0.0 0.0 52788 2800 ? S Aug28 0:00 | \_ /usr/sbin/CRON -f
root 13746 0.0 0.0 52788 2800 ? S Aug28 0:00 | \_ /usr/sbin/CRON -f
root 14592 0.0 0.0 52788 2800 ? S Aug28 0:00 | \_ /usr/sbin/CRON -f
root 15407 0.0 0.0 52788 2800 ? S Aug28 0:00 | \_ /usr/sbin/CRON -f
root 15425 0.0 0.0 52788 2800 ? S Aug28 0:00 | \_ /usr/sbin/CRON -f
root 16286 0.0 0.0 52788 2800 ? S Aug28 0:00 | \_ /usr/sbin/CRON -f
root 17115 0.0 0.0 52788 2800 ? S Aug28 0:00 | \_ /usr/sbin/CRON -f
root 17958 0.0 0.0 52788 2800 ? S Aug28 0:00 | \_ /usr/sbin/CRON -f
root 18838 0.0 0.0 52788 2800 ? S Aug28 0:00 | \_ /usr/sbin/CRON -f
root 19645 0.0 0.0 52788 2800 ? S Aug28 0:00 | \_ /usr/sbin/CRON -f
root 19671 0.0 0.0 52788 2800 ? S Aug28 0:00 | \_ /usr/sbin/CRON -f
root 20522 0.0 0.0 52788 2800 ? S Aug28 0:00 | \_ /usr/sbin/CRON -f
root 21377 0.0 0.0 52788 2800 ? S Aug28 0:00 | \_ /usr/sbin/CRON -f
root 22211 0.0 0.0 52788 2800 ? S Aug28 0:00 | \_ /usr/sbin/CRON -f
root 23052 0.0 0.0 52788 2800 ? S Aug28 0:00 | \_ /usr/sbin/CRON -f
root 23900 0.0 0.0 52788 2800 ? S Aug28 0:00 | \_ /usr/sbin/CRON -f
root 24743 0.0 0.0 52788 2800 ? S Aug28 0:00 | \_ /usr/sbin/CRON -f
Just happened again. https://i.imgur.com/Cb9cbXo.png
Tried to SSH to host
packet_write_wait: Connection to 192.168.0.16 port 22: Broken pipe
SSH to container worked. Reboot container, ping container until responds. SSH to container still works and now SSH to host is working fine. He. This is driving me bonkers.
This is what I came up with for a single host
- name: Check for Let's Encrypt certificate
block:
- name: Set default for variable
set_fact:
use_letsencrypt: false
- name: Get stat for cert file
stat:
path: /etc/letsencrypt/live/{{ hostname }}/cert.pem
register: certificate_file
- name: Set letsencrypt to true if certificate exists
set_fact:
use_letsencrypt: true
when: certificate_file.stat.exists
How can I make this more DRY? Pass it a hostname and it returns a true or false for the variable.
Edit: More info to make it more clear. It already works fine as is.
I want to use the above snippet for more than one host across different playbooks without copy and pasting the snippet every time.
I use the variable use_letsencrypt in different mail and web configuration files and would like to say, I'm busy setting up a config for example.com, do I have a cert for it.
I've been getting the following message every day from the apt-cacher-ng cron job:
/etc/cron.daily/apt-cacher-ng:
Error(s) occured while updating volatile index files for apt-cacher-ng.
Please visit http://proxy.localnet:3142/report.html to rerun the
expiration manually or check the error message(s) in the current log file(s).
When I run it, I always get errors on the exact same files. It is always the *.xz files.
An error occured while reading this file, some contents may have been ignored. Tag
Parsing metadata in debrep/dists/jessie/main/binary-amd64/Packages.xz
An error occured while reading this file, some contents may have been ignored. Tag
Parsing metadata in debrep/dists/jessie/main/binary-i386/Packages.xz
An error occured while reading this file, some contents may have been ignored. Tag
Parsing metadata in debrep/dists/jessie/main/source/Sources.xz
I delete them and the apt-cacher-ng web interface is happy, but as soon as I do an apt-get update on one of the clients. These files are back with exactly the same error.
I've been searching around for a solution to the, but can't seem to find anyone with this problem.
The box is still running PostgreSQL 8.1 and this started to increase a few weeks ago. It is only happening while the server is a bit busy.
fatal: pgsql:/etc/postfix/pgsql/relay_domains.cf(0,lock|fold_fix): table lookup problem
fatal: pgsql:/etc/postfix/pgsql/relay_domains.cf(0,lock|fold_fix): table lookup problem
fatal: pgsql:/etc/postfix/pgsql/relay_domains.cf(0,lock|fold_fix): table lookup problem
No other changes where made, so it seems to be related to a load increase. A new upgrade Debian Jessie box is in the works, but is there anything I can do in the meantime?
I have the following task
- name: Create users
user:
uid: "{{ item.uid }}"
name: "{{ item.username }}"
comment: "{{ item.comment }}"
shell: /bin/bash
groups: "{{ item.groups }}"
with_items: users
users contains all the users working in the company and I want to create all of them on the samba servers. But there are also 3 admins and I only want to create them in the other servers that is not in the samba group.
I can create the admin users with the above if I add
when: item.username in admin_users, but that will do it for all users and I want the default for new servers to be to only create the admin_users, but if the server is in the samba group, create all the users.
Will there be an easy way to do this? I'm thinking of splitting users into two group and create admin_user and other_users by running two tasks, but I would like to know if there is a DRY solution to this problem.
I started playing with MongoDB on Lucid. Now I would like to run a DB and Config server on the same box. They both use the same binary to launch, but with different config files and running on different ports. All directories for log and lib is split so one goes to mongodb and the other to mongoconf.
Each process can be started without any problems on their own.
start mongodb
stop mongodb
start mongoconf
stop mongoconf
But if I try to start both, the second one would just start and exit. Using 'initctl log-priority debug' I got the following in the logs.
Jan 6 12:44:12 mongo4 init: event_finished: Finished started event
Jan 6 12:44:12 mongo4 init: job_process_handler: Ignored event 1 (1) for process 5690
Jan 6 12:44:12 mongo4 init: mongoconf (mongoconf) main process (5690) terminated with status 1
Jan 6 12:44:12 mongo4 init: mongoconf (mongoconf) goal changed from start to stop
Jan 6 12:44:12 mongo4 init: mongoconf (mongoconf) state changed from running to stopping
man 5 init shows that you can use instance names to differentiate the two. I tried using 'instance mongoconf' in the on upstart script and 'instance mongodb' in the other one, and it still fails. I can manually start the other process, so there is definitely no conflicts on port numbers or directories.
Any ideas on what to try or how to get output on why it is 'terminated with status 1'?
Thanx