19 Srp
2016
19 Srp
'16
15:36
Hello everyone
I have some remarks about starting FRED components automatically after boot in Ubuntu
16.04 LTS
xenial. If anyone has some input, please share.
First, I suspect that upstart job definitions are obsolete and should removed. I mean the
files:
/etc/init/fred-adifd.conf
/etc/init/fred-logd.conf
/etc/init/fred-msgd.conf
/etc/init/fred-pifd.conf
/etc/init/fred-rifd.conf
Next, right after installation the services of FRED were not enabled, hence:
# cd /lib/systemd/system
# systemctl enable fred*
This is not enough, since fred-pyfred failed because it was started too early (before
omniorb name
server), therefore I modified unit definition of fred-pyfred in
/lib/systemd/system/fred-pyfred.service
so now it looks like this:
[Unit]
Description=fred-pyfred
After=omniorb4-nameserver.service
#ConditionPathExists=!/etc/ssh/sshd_not_to_be_run
Requires=omniorb4-nameserver.service
[Service]
User=fred
WorkingDirectory=/
StandardOutput=null
StandardError=null
ExecStart=/usr/sbin/fred-pyfred -d
KillMode=process
Restart=on-failure
[Install]
WantedBy=multi-user.target
and generates the following result:
# systemd-analyze critical-chain fred-pyfred.service
The time after the unit is active or started is printed after the "@"
character.
The time the unit takes to start is printed after the "+" character.
fred-pyfred.service @6.814s
└─omniorb4-nameserver.service @6.774s +23ms
└─network-online.target @6.764s
└─NetworkManager-wait-online.service @927ms +5.837s
└─NetworkManager.service @665ms +185ms
└─dbus.service @639ms
└─basic.target @639ms
└─sockets.target @639ms
└─snapd.socket @637ms +1ms
└─sysinit.target @634ms
└─swap.target @634ms
└─dev-disk-by\x2duuid-d8b40e4d\x2d4e62\x2d4436\x2db09b\x2d8cfc2a2d8a1d.swap
@629ms +3ms
└─dev-disk-by\x2duuid-d8b40e4d\x2d4e62\x2d4436\x2db09b\x2d8cfc2a2d8a1d.device
@623ms
(of course your delays will vary).
To check if FRED services are running, one may use
# systemctl status fred*
Maybe this page could get an update? https://fred.nic.cz/page/2906/installation-ubuntu/
Best regards
Piotr Przybył
19 Srp
19 Srp
15:58
On 19 Aug 2016 at 15:36, Piotr Przybyl wrote:
Hello everyone
I have some remarks about starting FRED components automatically after boot in Ubuntu
16.04 LTS
xenial. If anyone has some input, please share.
We have similar issues starting FRED automatically on boot in Fedora.
Right now we are starting FRED manually every time we reboot the system. We would
greatly benefit if anyone had a good autostart method for FRED on Fedora as well.
Regards,
Paulos
======================
Dr Paulos B Nyirenda
NIC.MW & .mw ccTLD
http://www.registrar.mw
First, I suspect that upstart job definitions are obsolete and should removed. I mean the
files:
/etc/init/fred-adifd.conf
/etc/init/fred-logd.conf
/etc/init/fred-msgd.conf
/etc/init/fred-pifd.conf
/etc/init/fred-rifd.conf
Next, right after installation the services of FRED were not enabled, hence:
# cd /lib/systemd/system
# systemctl enable fred*
This is not enough, since fred-pyfred failed because it was started too early (before
omniorb name
server), therefore I modified unit definition of fred-pyfred in
/lib/systemd/system/fred-pyfred.service
so now it looks like this:
[Unit]
Description=fred-pyfred
After=omniorb4-nameserver.service
#ConditionPathExists=!/etc/ssh/sshd_not_to_be_run
Requires=omniorb4-nameserver.service
[Service]
User=fred
WorkingDirectory=/
StandardOutput=null
StandardError=null
ExecStart=/usr/sbin/fred-pyfred -d
KillMode=process
Restart=on-failure
[Install]
WantedBy=multi-user.target
and generates the following result:
# systemd-analyze critical-chain fred-pyfred.service
The time after the unit is active or started is printed after the "@"
character.
The time the unit takes to start is printed after the "+" character.
fred-pyfred.service @6.814s
+-omniorb4-nameserver.service @6.774s +23ms
+-network-online.target @6.764s
+-NetworkManager-wait-online.service @927ms +5.837s
+-NetworkManager.service @665ms +185ms
+-dbus.service @639ms
+-basic.target @639ms
+-sockets.target @639ms
+-snapd.socket @637ms +1ms
+-sysinit.target @634ms
+-swap.target @634ms
+-dev-disk-by\x2duuid-d8b40e4d\x2d4e62\x2d4436\x2db09b\x2d8cfc2a2d8a1d.swap
@629ms +3ms
+-dev-disk-by\x2duuid-d8b40e4d\x2d4e62\x2d4436\x2db09b\x2d8cfc2a2d8a1d.device
@623ms
(of course your delays will vary).
To check if FRED services are running, one may use
# systemctl status fred*
Maybe this page could get an update? https://fred.nic.cz/page/2906/installation-ubuntu/
Best regards
Piotr Przybyl
_______________________________________________
fred-users mailing list
fred-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/fred-users
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2016.0.7752 / Virus Database: 4647/12837 - Release Date: 08/19/16
16:07
Since Ubuntu 16.04, both Ubuntu and Fedora are using systemd so it will
be easier to maintain startup scripts. I'll evaluate Piotr's
suggestions and try to put them into the distribution for both of these
systems.
Jaromir
On Fri, 2016-08-19 at 15:58 +0200, Dr Paulos B Nyirenda wrote:
On 19 Aug 2016 at 15:36, Piotr Przybyl wrote:
--
Jaromir Talir
Technicky partner / Technical Fellow
-------------------------------------------
CZ.NIC, z.s.p.o. -- .cz domain registry
Milesovska 5, 130 00 Praha 3, Czech Republic
mailto:jaromir.talir@nic.cz http://nic.cz/
sip:jaromir.talir@nic.cz tel:+420.222745107
mob:+420.739632712 fax:+420.222745112
-------------------------------------------
Hello everyone
I have some remarks about starting FRED components automatically
after boot in Ubuntu 16.04 LTS
xenial. If anyone has some input, please share.
We have similar issues starting
FRED automatically on boot in Fedora.
Right now we are starting FRED manually every time we reboot the
system. We would
greatly benefit if anyone had a good autostart method for FRED on
Fedora as well.
Regards,
Paulos
======================
Dr Paulos B Nyirenda
NIC.MW & .mw ccTLD
http://www.registrar.mw
First, I suspect that upstart job definitions are obsolete and
should removed. I mean the files:
/etc/init/fred-adifd.conf
/etc/init/fred-logd.conf
/etc/init/fred-msgd.conf
/etc/init/fred-pifd.conf
/etc/init/fred-rifd.conf
Next, right after installation the services of FRED were not
enabled, hence:
# cd /lib/systemd/system
# systemctl enable fred*
This is not enough, since fred-pyfred failed because it was started
too early (before omniorb name
server), therefore I modified unit definition of fred-pyfred in
/lib/systemd/system/fred-pyfred.service
so now it looks like this:
[Unit]
Description=fred-pyfred
After=omniorb4-nameserver.service
#ConditionPathExists=!/etc/ssh/sshd_not_to_be_run
Requires=omniorb4-nameserver.service
[Service]
User=fred
WorkingDirectory=/
StandardOutput=null
StandardError=null
ExecStart=/usr/sbin/fred-pyfred -d
KillMode=process
Restart=on-failure
[Install]
WantedBy=multi-user.target
and generates the following result:
# systemd-analyze critical-chain fred-pyfred.service
The time after the unit is active or started is printed after the
"@" character.
The time the unit takes to start is printed after the "+"
character.
fred-pyfred.service @6.814s
+-omniorb4-nameserver.service @6.774s +23ms
+-network-online.target @6.764s
+-NetworkManager-wait-online.service @927ms +5.837s
+-NetworkManager.service @665ms +185ms
+-dbus.service @639ms
+-basic.target @639ms
+-sockets.target @639ms
+-snapd.socket @637ms +1ms
+-sysinit.target @634ms
+-swap.target @634ms
+-dev-disk-by\x2duuid-
d8b40e4d\x2d4e62\x2d4436\x2db09b\x2d8cfc2a2d8a1d.swap
@629ms +3ms
+-dev-disk-by\x2duuid-
d8b40e4d\x2d4e62\x2d4436\x2db09b\x2d8cfc2a2d8a1d.device
@623ms
(of course your delays will vary).
To check if FRED services are running, one may use
# systemctl status fred*
Maybe this page could get an update? https://fred.nic.cz/page/2906/
installation-ubuntu/
Best regards
Piotr Przybyl
_______________________________________________
fred-users mailing list
fred-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/fred-users
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2016.0.7752 / Virus Database: 4647/12837 - Release Date:
08/19/16
_______________________________________________
fred-users mailing list
fred-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/fred-users
21 Srp
21 Srp
11:43
On 19 Aug 2016 at 17:27, Piotr Przybyl wrote:
On 19/08/16 15:58, Dr Paulos B Nyirenda wrote:
Running FRED in production on .mw registry, yes, very much so. Why the question?
We have been testing FRED since 2013 and we moved to production phase a few months
ago.
Regards,
Paulos
======================
Dr Paulos B Nyirenda
NIC.MW & .mw ccTLD
http://www.registrar.mw
We have similar issues starting FRED automatically on boot in Fedora.
Are you running production/live version using Fedora?
Best regards
Piotr Przybyl
_______________________________________________
fred-users mailing list
fred-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/fred-users
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2016.0.7752 / Virus Database: 4647/12837 - Release Date: 08/19/16
15:03
On 21/08/16 11:43, Dr Paulos B Nyirenda wrote:
On 19 Aug 2016 at 17:27, Piotr Przybyl wrote:
Well, some people say that some distros having bleeding edge features but lacking long
term support
might not be the best choice for running a prod server in a long term, although this also
depends on
one's needs and context. "Don't use Fedora for server" can't be
taken as a dogma. ;-)
Fedora is released every 6 months (just like Ubuntu for instance), and is supported for 13
months
after release. This is in contrast to Ubuntu LTS, which is supported for 5 years after the
release.
I'm not RHEL or CentOS certified pro and AFAICT the "redhatish" distros have
testing field in
Fedora, then features well tested in desktop environments are incorporated into
RHEL/CentOS.
Best regards
Piotr Przybył
On 19/08/16 15:58, Dr Paulos B Nyirenda wrote:
Running FRED in production on .mw registry, yes, very much so. Why the question?
We have been testing FRED since 2013 and we moved to production phase a few months
ago.
We have similar issues starting FRED automatically on boot in Fedora.
Are you running production/live version using Fedora?
2817
days inactive
2819
days old
5 comments
3 participants
participants (3)
-
Dr Paulos B Nyirenda -
Jaromir Talir -
Piotr Przybył