Re: [CentOS] Running amanda on CentOS 7: "amanda-udp.service failed."
On 3/17/20 7:03 AM, Robert Heller wrote: I am trying to get amanda backup going on a CentOS 7 system and things are not working: sharky4.deepsoft.com% sudo systemctl start amanda-udp [sudo] password for heller: Job for amanda-udp.service failed because a configured resource limit was exceeded. See "systemctl status amanda-udp.service" and "journalctl -xe" for details. sharky4.deepsoft.com% sudo systemctl status -l amanda-udp â—� amanda-udp.service - Amanda Backup System Loaded: loaded (/usr/lib/systemd/system/amanda-udp.service; static; vendor preset: disabled) Active: failed (Result: resources) You don't start the service directly. Start and enable the socket and then it will start the service when a connection is made. systemctl enable amanda-udp.socket systemctl start amanda-udp.socket -- Orion Poplawski Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 https://www.nwra.com/ ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] signing modules
> On Mar 17, 2020, at 07:34, Jerry Geis wrote: > > I only have one problem with this... many of my systems are remote. I "will > not" be able to remotely enter the MOK and accept the certs etc... How do I > get around this? Recall that my hardware (NUC7C) does not allow to disable > UEFI. So I have to use UEFI. This is the point of secure boot, a remote user can’t make it load malicious kernel modules. -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Running amanda on CentOS 7: "amanda-udp.service failed."
At Tue, 17 Mar 2020 09:37:24 -0600 CentOS mailing list
wrote:
>
> Content-Language: en-US
>
> Hi Robert -
>
> I'm running it successfully on C7 using xinetd.ÃÂ Do you have
> documentation for running it directly from systemd?ÃÂ Working xinetd
I just install amanda-client and that created the systemd service files, which
I presumed was how things were supposed to work now.
I guess I will install xinetd and go from there instead.
> configuration:
>
> cat /etc/xinetd.d/amanda
> # default: off
> # description:ÃÂ The client for the Amanda backup system.\
> #ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ This must be on for
> systems being backed up\
> #ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ by Amanda.
> service amanda
> {
> ÃÂ ÃÂ ÃÂ disableÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ = no
> ÃÂ ÃÂ ÃÂ socket_typeÃÂ ÃÂ ÃÂ ÃÂ = dgram
> ÃÂ ÃÂ ÃÂ protocolÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ = udp
> ÃÂ ÃÂ ÃÂ waitÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ = yes
> ÃÂ ÃÂ ÃÂ userÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ = amandabackup
> ÃÂ ÃÂ ÃÂ groupÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ = disk
> ÃÂ ÃÂ ÃÂ serverÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ = /usr/sbin/amandad
> # Configure server_args for the authentication type you will be using,
> # and the services you wish to allow the amanda server and/or recovery
> # clients to use.
> #
> # Change the -auth= entry to reflect the authentication type you use.
> # Add amindexd to allow recovery clients to access the index database.
> # Add amidxtaped to allow recovery clients to access the tape device.
> ÃÂ ÃÂ ÃÂ server_argsÃÂ ÃÂ ÃÂ ÃÂ = -auth=bsd amdump
> ÃÂ ÃÂ ÃÂ flagsÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ = IPv4
> }
>
> Cheers,
> Dave
>
> On 3/17/20 7:03 AM, Robert Heller wrote:
> > I am trying to get amanda backup going on a CentOS 7 system and things are
> > not
> > working:
> >
> > sharky4.deepsoft.com% sudo systemctl start amanda-udp
> > [sudo] password for heller:
> > Job for amanda-udp.service failed because a configured resource limit was
> > exceeded. See "systemctl status amanda-udp.service" and "journalctl -xe"
> > for details.
> > sharky4.deepsoft.com% sudo systemctl status -l amanda-udp
> > âÃÂàamanda-udp.service - Amanda Backup System
> > Loaded: loaded (/usr/lib/systemd/system/amanda-udp.service; static;
> > vendor preset: disabled)
> > Active: failed (Result: resources)
> >
> > Mar 17 08:35:58 sharky4.deepsoft.com systemd[1]: Unit amanda-udp.service
> > entered failed state.
> > Mar 17 08:35:58 sharky4.deepsoft.com systemd[1]: amanda-udp.service failed.
> > Mar 17 08:43:00 sharky4.deepsoft.com systemd[1]: Got more than one socket.
> > Mar 17 08:43:00 sharky4.deepsoft.com systemd[1]: amanda-udp.service failed
> > to run 'start' task: Invalid argument
> > Mar 17 08:43:00 sharky4.deepsoft.com systemd[1]: Failed to start Amanda
> > Backup System.
> > Mar 17 08:43:00 sharky4.deepsoft.com systemd[1]: amanda-udp.service failed.
> > Mar 17 08:52:24 sharky4.deepsoft.com systemd[1]: Got more than one socket.
> > Mar 17 08:52:24 sharky4.deepsoft.com systemd[1]: amanda-udp.service failed
> > to run 'start' task: Invalid argument
> > Mar 17 08:52:24 sharky4.deepsoft.com systemd[1]: Failed to start Amanda
> > Backup System.
> > Mar 17 08:52:24 sharky4.deepsoft.com systemd[1]: amanda-udp.service failed.
> > sharky4.deepsoft.com% sudo journalctl -xe
> > Mar 17 08:52:24 sharky4.deepsoft.com systemd[1]: amanda-udp.service failed
> > to
> > Mar 17 08:52:24 sharky4.deepsoft.com systemd[1]: Failed to start Amanda
> > Backup
> > -- Subject: Unit amanda-udp.service has failed
> > -- Defined-By: systemd
> > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> >
> > ___
> > CentOS mailing list
> > CentOS@centos.org
> > https://lists.centos.org/mailman/listinfo/centos
>
--
Robert Heller -- 978-544-6933 Cell: 413-658-7953 GV: 978-633-5364
Deepwoods Software-- Custom Software Services
http://www.deepsoft.com/ -- Linux Administration Services
hel...@deepsoft.com -- Webhosting Services
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Running amanda on CentOS 7: "amanda-udp.service failed."
Hi Robert -
I'm running it successfully on C7 using xinetd. Do you have
documentation for running it directly from systemd? Working xinetd
configuration:
cat /etc/xinetd.d/amanda
# default: off
# description: The client for the Amanda backup system.\
# This must be on for systems being backed up\
# by Amanda.
service amanda
{
disable = no
socket_type = dgram
protocol = udp
wait = yes
user = amandabackup
group = disk
server = /usr/sbin/amandad
# Configure server_args for the authentication type you will be using,
# and the services you wish to allow the amanda server and/or recovery
# clients to use.
#
# Change the -auth= entry to reflect the authentication type you use.
# Add amindexd to allow recovery clients to access the index database.
# Add amidxtaped to allow recovery clients to access the tape device.
server_args = -auth=bsd amdump
flags = IPv4
}
Cheers,
Dave
On 3/17/20 7:03 AM, Robert Heller wrote:
I am trying to get amanda backup going on a CentOS 7 system and things are not
working:
sharky4.deepsoft.com% sudo systemctl start amanda-udp
[sudo] password for heller:
Job for amanda-udp.service failed because a configured resource limit was exceeded. See
"systemctl status amanda-udp.service" and "journalctl -xe" for details.
sharky4.deepsoft.com% sudo systemctl status -l amanda-udp
â—� amanda-udp.service - Amanda Backup System
Loaded: loaded (/usr/lib/systemd/system/amanda-udp.service; static; vendor
preset: disabled)
Active: failed (Result: resources)
Mar 17 08:35:58 sharky4.deepsoft.com systemd[1]: Unit amanda-udp.service
entered failed state.
Mar 17 08:35:58 sharky4.deepsoft.com systemd[1]: amanda-udp.service failed.
Mar 17 08:43:00 sharky4.deepsoft.com systemd[1]: Got more than one socket.
Mar 17 08:43:00 sharky4.deepsoft.com systemd[1]: amanda-udp.service failed to
run 'start' task: Invalid argument
Mar 17 08:43:00 sharky4.deepsoft.com systemd[1]: Failed to start Amanda Backup
System.
Mar 17 08:43:00 sharky4.deepsoft.com systemd[1]: amanda-udp.service failed.
Mar 17 08:52:24 sharky4.deepsoft.com systemd[1]: Got more than one socket.
Mar 17 08:52:24 sharky4.deepsoft.com systemd[1]: amanda-udp.service failed to
run 'start' task: Invalid argument
Mar 17 08:52:24 sharky4.deepsoft.com systemd[1]: Failed to start Amanda Backup
System.
Mar 17 08:52:24 sharky4.deepsoft.com systemd[1]: amanda-udp.service failed.
sharky4.deepsoft.com% sudo journalctl -xe
Mar 17 08:52:24 sharky4.deepsoft.com systemd[1]: amanda-udp.service failed to
Mar 17 08:52:24 sharky4.deepsoft.com systemd[1]: Failed to start Amanda Backup
-- Subject: Unit amanda-udp.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
--
"They that can give up essential liberty to obtain a little temporary safety deserve
neither safety nor liberty."
-- Benjamin Franklin
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Xorg on CentOS
HI James - Nice trick. Thanks. Jerry ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Xorg on CentOS
Jerry Geis wrote: I am trying to find a way to tell the ORDER of X drivers. I have a VM image of CentOS 7. If I boot the image I want the generic driver to load. But if I put that image on hardware I want the Intel driver to load. So if I specific the /etc/X11/xorg.conf.d/20-intel.conf and specify Intel - this is great for the physical device. But booting my image it fails cause there is not Intel hardware. How can have ONE X config that specifies Intel first and if not present load generic VGA stuff. Thanks, You could write a display-manager.service ExecStartPre script that copies/removes the required file(s) to/from /etc/X11/xorg.conf.d/ depending on the hardware it finds? i.e. create a file like /etc/systemd/system/display-manager.service.d/hardware.conf containing: [Service] ExecStartPre=-/path/to/my/custom/hardware/script I do something similar - which works fine James Pearson ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Xorg on CentOS
I am trying to find a way to tell the ORDER of X drivers. I have a VM image of CentOS 7. If I boot the image I want the generic driver to load. But if I put that image on hardware I want the Intel driver to load. So if I specific the /etc/X11/xorg.conf.d/20-intel.conf and specify Intel - this is great for the physical device. But booting my image it fails cause there is not Intel hardware. How can have ONE X config that specifies Intel first and if not present load generic VGA stuff. Thanks, Jerry ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Running amanda on CentOS 7: "amanda-udp.service failed."
I am trying to get amanda backup going on a CentOS 7 system and things are not working: sharky4.deepsoft.com% sudo systemctl start amanda-udp [sudo] password for heller: Job for amanda-udp.service failed because a configured resource limit was exceeded. See "systemctl status amanda-udp.service" and "journalctl -xe" for details. sharky4.deepsoft.com% sudo systemctl status -l amanda-udp â amanda-udp.service - Amanda Backup System Loaded: loaded (/usr/lib/systemd/system/amanda-udp.service; static; vendor preset: disabled) Active: failed (Result: resources) Mar 17 08:35:58 sharky4.deepsoft.com systemd[1]: Unit amanda-udp.service entered failed state. Mar 17 08:35:58 sharky4.deepsoft.com systemd[1]: amanda-udp.service failed. Mar 17 08:43:00 sharky4.deepsoft.com systemd[1]: Got more than one socket. Mar 17 08:43:00 sharky4.deepsoft.com systemd[1]: amanda-udp.service failed to run 'start' task: Invalid argument Mar 17 08:43:00 sharky4.deepsoft.com systemd[1]: Failed to start Amanda Backup System. Mar 17 08:43:00 sharky4.deepsoft.com systemd[1]: amanda-udp.service failed. Mar 17 08:52:24 sharky4.deepsoft.com systemd[1]: Got more than one socket. Mar 17 08:52:24 sharky4.deepsoft.com systemd[1]: amanda-udp.service failed to run 'start' task: Invalid argument Mar 17 08:52:24 sharky4.deepsoft.com systemd[1]: Failed to start Amanda Backup System. Mar 17 08:52:24 sharky4.deepsoft.com systemd[1]: amanda-udp.service failed. sharky4.deepsoft.com% sudo journalctl -xe Mar 17 08:52:24 sharky4.deepsoft.com systemd[1]: amanda-udp.service failed to Mar 17 08:52:24 sharky4.deepsoft.com systemd[1]: Failed to start Amanda Backup -- Subject: Unit amanda-udp.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit amanda-udp.service has failed. -- -- The result is failed. Mar 17 08:52:24 sharky4.deepsoft.com systemd[1]: amanda-udp.service failed. sharky4.deepsoft.com% cat /usr/lib/systemd/system/amanda-udp.service [Unit] Description=Amanda Backup System After=local-fs.target [Service] User=amandabackup Group=disk ExecStart=/usr/sbin/amandad -auth=bsd amdump StandardInput=socket What is missing? I have installed (stock CentOS 7 from standard repos): sharky4.deepsoft.com% rpm -qa amanda\* amanda-server-3.3.3-21.el7.x86_64 amanda-client-3.3.3-21.el7.x86_64 amanda-libs-3.3.3-21.el7.x86_64 amanda-3.3.3-21.el7.x86_64 -- Robert Heller -- 978-544-6933 Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software-- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services hel...@deepsoft.com -- Webhosting Services ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] signing modules
Hi Phil, Your correct. I missed a step about importing the key: mokutil --import MOK.der So then I rebooted entered teh MOK, accepted all certs and rebooted and it loaded. I only have one problem with this... many of my systems are remote. I "will not" be able to remotely enter the MOK and accept the certs etc... How do I get around this? Recall that my hardware (NUC7C) does not allow to disable UEFI. So I have to use UEFI. Thanks for all the suggestions. Jerry ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] tuned on CentOS 6.9
Does tuned on CentOS 6.9 (i.e. tuned-0.2.19-18.el6.noarch) do any dynamic tuning, or does it only support static configuration via a static profile? Chris ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
