Probably fine now we've dropped support for LXC containers, and improved firewalld for Equatower in rOPS9f24b9df2f44.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Feb 14 2020
Hypervisor configuration is now fine.
Feb 12 2020
Kernel upgraded do 12.1-p2.
The event triggered the consume of all RAM is probably the @MaxChan eggdrop.
Feb 11 2020
Feb 10 2020
As the port is maintained, the best course of action is to send a patch for this port upstream.
Works fine on WindRiver with ImageMagick 7 and Wikimedia Commons pictures of the day from February 2020 as test:
We can wait upstream updates for the ImageMagick 7 API, especially as upstream was active in November 2019.
D2203 takes care of the automatic update.
There is currently no auto update for ports tree:
Upgraded to last 12.0 version, 12.0-p13.
Good to know. You're welcome.
i m sucessful to login .. thanks
note.. i try login now
Feb 9 2020
Feb 8 2020
Feb 6 2020
It's remove according current Ysul configuration and rOPS.
Feb 5 2020
Normally done everywhere. Should check Dwellers when we respawn it.
DNS have been published, server is configured to listen to those ports, Docker container too.
Feb 4 2020
Previously already published
The server works fine. Next step is to integrate Certbot or any other client with it and create relevant CNAMEs.
Server is deployed on Equatower.
Jan 31 2020
It seems it's also possible to store the deploy key on the master, as long as it's fine to copy it to the server:
Jan 28 2020
Jan 25 2020
D2151 works well, but there are two issues:
Perhaps a master key would be more pertinent, if so, that's a candidate for Vault.
We've a deploy key in salt master, let's use it.
Roles core and saltmaster have been successfully fixed and applied.
Jan 21 2020
Jan 20 2020
After a few dozens of seconds, I've got:
Fun, after systemctl enable --now snapd.socket I got the following message: