search for: servernames

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9 Severity: critical Justification: breaks the whole system Dear Maintainer, After upgrading the R610 server from Debian 7 to Debian 8, the dom0 becomes unresponsive via ssh after an hour or so, although the domUs still remain accessible. Initially we thought it may be a disk space issue on / or /boot so action was taken to increase those

Hey list, Recently I've gotten my Samba PDC to successfully use an OpenLDAP backend, while using the smbk5pwd and ppolicy overlays for OpenLDAP. However, Samba appears to incorrectly handle responses from LDAP's ppolicy overlay, even though it very clearly receives them. If I enter in a password (be it through Ctrl+Alt+Delete or when a password expires and the user is prompted at logon)

Samba is a domain member server authenticating to a MS-Windows domain controller. With 3.0.7 and all previous version for the past few years I could map a Windows to Unix userid in the username map file like so.. fred = fredw His home directory was then accessible as \\servername\fredw so \\servername\%username% from a Windows NTx client. I make EXTENSIVE use of that functionality. I missed

Hello, I have this defined resource type which is working perfectly until I want an ssl an http vhost pointing to the same directory in which case the unique $servername variable became a singleton Do you have any idea how to get around this? I am pretty tired at the moment and cant think of any good solution. define vhost ($servername = "${hostname}.${domain}", $serveralias = [

Hello I recently bought a small UPS by Eaton (Ellipse ECO 800) in order to prevent my btrfs-fileserver (running Debian 12 Bookworm 12.4 from shutting down abruptly while writing something important during a power loss. I am using the version 2.8.0.7 provided by Debian. I have found very gooddocumentation on how to set up the UPS and the services on the server connected to it. Unfortunately

Just updated one of our servers, and see a bunch of udevd-event[8735]: run_program: ressize 256 too short Along with Apr 8 14:57:48 <servername> kernel: Breaking affinity for irq 209 Apr 8 14:57:48 <servername> kernel: CPU 8 is now offline Apr 8 14:57:49 <servername> kernel: CPU 8 offline: Remove Rx thread Apr 8 14:57:49 <servername> kernel: CPU 9 is now offline Apr

Hello list, Postfix is dying on one of my servers almost nightly. This system is running CentOS5 with postfix-2.3.3-2. In the morning (after noticing it died) I try to run `service postfix stop` and I get a failed start. Running `ps ax | grep postfix` I can see one process still running for postfix. After killing this, I am able to run `service postfix start`. I see a lot of this in my

On several occasions I have seen the apcsmart process runaway using 100% CPU while filling my syslog partition by logging the following syslog entries at an incredible rate. I have seen up to 21,800 log entries PER SECOND of the following nature: --[snip]-- Jun 25 10:06:38 servername apcsmart[4012]: Communications with UPS lost: Communications with UPS lost - check cabling Jun 25 10:06:38

Well, from your logs it seems that at 05:17:03 your nut-server (upsd) restarted, so an upsmon reconnection attempt at 05:17:09 had an issue with that (config not all applied? strange a bit) but since 05:17:14 it is okay. Maybe a few too many banners shown from upsmon, while its same uptime seems to continue. Maybe someone should check on that, seems like a good and easy newcomer issue to learn

The recently-left programmer did *something*, and he didn't know what, and the guy who picked it up is working with me to find out why /var/log/messages is getting flooded with Oct 26 11:01:06 <servername> kernel: type=1105 audit(1477494066.569:642430): pid=108551 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:unconfined_service_t:s0 msg='op=PAM:session_open

On 19.01.24 09:00, Jim Klimov via Nut-upsuser wrote: >Well, from your logs it seems that at 05:17:03 your nut-server (upsd) >restarted, so an upsmon reconnection attempt at 05:17:09 had an issue with >that (config not all applied? strange a bit) but since 05:17:14 it is okay. > >Maybe a few too many banners shown from upsmon, while its same uptime seems >to continue. Maybe

We have a client-server puppetmaster running puppetd and puppetmasterd, however I would like to test configurations locally before committing the changes on the puppetmaster. Running the puppet config locally with /usr/bin/puppet mostly works. The thing that fails ( which I have commented out on my local copy to test everything else ) is a erb template for puppet.conf that includes:

I''m wondering if anyone might have any suggestions... We''ve installed CentOS5.2 on 3 servers and have an FC switch, dual-port cards, and FC RAID device. We configured the RAID as two separate logical RAIDs. One is RAID-10 for speed and it hosts Xen VM images as LVs. The rest of the drive is RAID-5 to maximize space and houses a lot of lighter access data on a GFS2 filesystem.

With recent NUT releases, driver disconnections should be contained in its own `nut-driver at eaton` instance (the `@upsname` part is derived from the `ups.conf` section name). One of the drivers failing and restarting is not a proper cause for the data server to recycle. Also, nowadays some (maybe not all) USB-capable drivers should try to reconnect without restarting. Note however, that in some

Our puppetmaster runs on a host with multiple interfaces connected to various private networks, with different hostnames for each IP. I''m trying to use $servername in modules to copy files over a private network, but this is always set to the public hostname of the server. That route is blocked by a firewall. Is there a way to use the server variable in puppet.conf in manifests?

Hello and thanks for all the replies. This morning at 9:50 the server stopped working unexpectedly - I was still sleeping until 10:00, so no user intervention took place. Jan 19 05:50:17 mars nut-server[1303]: mainloop: Interrupted system call Jan 19 05:50:17 mars nut-server[1303]: Signal 15: exiting Jan 19 05:50:17 mars nut-server[1303]: Network UPS Tools upsd 2.8.0 Jan 19 05:50:17 mars

I''m having some issues trying to track down a problem I''m having parsing a simple template, using create_resources and Hiera. Here''s my setup (abridged): ../hieradata/settings.yaml: *global:* * variables:* * env: foo* * * *appSpecific:* * serverName: someServer* ../modules/test/manifests/init.pp: *class test {* * create_resources(test::variables,

I've just added the following to the CentOS bugtracker for CentOS-7 0009860. I admit to not being sure if it's the same issue, or a separate one, but this and other Dell servers - I *think* they're all R420's, but I could be wrong, just all do the same thing on boot. ***************** I've just updated a CentOS 7 server to the latest kernel, vmlinuz-3.10.0-327.4.5.el7.x86_64,

On 19.01.24 16:20, Stefan Schumacher via Nut-upsuser wrote: >This morning at 9:50 the server stopped working unexpectedly - I was >still sleeping until 10:00, so no user intervention took place. > >Jan 19 05:50:17 mars nut-server[1303]: mainloop: Interrupted system call >Jan 19 05:50:17 mars nut-server[1303]: Signal 15: exiting >Jan 19 05:50:17 mars nut-server[1303]: Network UPS

Ok, folks, I don't get this one at all. I've got a server that I just rebuilt last week, from C5 to C7. It used to export filesystems. Those were moved to another server, and NFS wasn't turned up when I built it. I just turned it down again. And yet, I see Mar 14 10:26:33 <servername> systemd: Job dev-disk-by\x2dlabel-export1.device/start timed out. Mar 14 10:26:33