similar to: odd behavior with provider yum...

Hi. trying to get a domU (dom1) up using nfs root. never done this before ;-). I have dom0 up (2.6.12-xen0) and i have an external nfs server with a nice root disk populated. i get this after xm create -c dom1 vmid=1 . . . IP-Config: Complete: device=eth0, addr=172.31.205.229, mask=255.255.255.0, gw=172.31.205.2, host=vm%d, domain=, nis-domain=(none),

I have been googling and searching the archive , haven''t got anything helpful. Would appreciate any help. Got the follow error when trying to start a domain using NFS root IP-Config: Incomplete network configuration information. Looking up port of RPC 100003/2 on 10.10.24.141 <http://10.10.24.141> RPC: sendmsg returned error 101 portmap: RPC call returned error 101 Root-NFS:

Greetings all, My deployment of puppet includes a monitrc to make sure that puppetd stays up and running. It seems like (across all of my hosts) that pupeptd will end up dying and restarted by monit. I''m running puppetd under a screen session now on one particular host with --debug --verbose to see if any thing comes out on console but until it happens again, any anybody else

I''m curious if anybody else has seen this behavior.... Right now I have puppetd making sure that NFS and NTP services are running across a group of hosts, and if for some reason those services are not running, puppet will happily start them up for me. The catch is, in my environment we''re pushing towards IPv6 except for customer facing equipment. So when puppet comes along and

I see in the changelog that: You now must specify an environment and you are required to specify the valid environments for your site. (#911) Does this mean that the puppetmaster has to be updated before clients work correctly? I ask because I''m testing out a client upgrade to 0.24.0 (server is still 0.23.2) and this is what I''m seeing: [~]% sudo /foo/bin/puppetd

Hello, I''ve installed a OpenSolaris dom0 snv_44 on a x4100 server, and booted a 32-bit xen kernel. I''m trying to create a OpenSolaris DOMU (snv_44) by following the howto described at http://www.opensolaris.org/os/community/xen/howto/create-osox-domu/. I did not manage to create a diskless environment by using SUNWCXall. I''ve created SUNWCreq instead and add the

Hi all, I want to map an NFS share from a remote server to a local CentOS 5.4 server, but have a problem with portmap: root at mercury:[~]$ service portmap restart pmap_getmaps rpc problem: RPC: Unable to receive; errno = Connection reset by peer Stopping portmap: [FAILED] Starting portmap: [ OK ] root at

I think that I''m running into the warning on external node support here but after a recent upgrade for my puppetmaster I get: puppetmasterd[19397]: Could not find aa0-006-4.foo.com with names aa0-006-4.foo.com, aa0-006-4 I''ve not changed puppetd.conf which contains: ldapnodes = true ldapserver = my.ldap.foo.com ldapbase = ou=hosts,dc=foo,dc=com I''ve not

I don't know if this is RedHat 5.1 specific, but be aware that the version of portmap distributed is the enhanced (Wietse Venema) version. That's great, except for two things. The first is documented, but easy to overlook: "In order to avoid deadlocks, the portmap program does not attempt to look up the remote host name or user name...The upshot of all this is that only network

Has anyone done rollbacks with puppet? The story goes that last night I pushed a change out, which intentionally changed the way certain services where managed. The change involved pushing out a few files, cronjobs, etc., which was okay until it was discovered there was a bug with the service. My configurations are kept in subversion and rolling back to a previous configuration would have

Hi, I have a same question posted by punamia , when I am trying to create domain using xen-2.0 built on Fedora 2/ Pentium PC with IDE drive: "Kernel panic: No init found. Try passing init= option to kernel". Below is console dump. Any suggestions ? Thanks Console Dump: Linux version 2.6.8.1-xenU (root@localhost.localdomain) (gcc version 3.3.3 20040412 (Red Hat Linux

Are there any known vulnerabilities in portmap (redhat''s portmap-4.0-7b)? I''ve been receiving a lot of attempts to access the portmap port on some linuxppc machines I administer by various machines which clearly have no business with mine, and I wonder if this is an attempt to break in to my machines. I''ve searched some archives, but I haven''t yet found any

I am attempting to move our test puppet installation from looking for node information in a manifest to LDAP. I followed the instructions at: https://reductivelabs.com/trac/puppet/wiki/LdapNodes and was able to get the puppet schema loaded into our LDAP. I can now query LDAP and modify/load data without any issues using the OpenLDAP tools. e.g. ldapsearch -h ldapdev1.domain.com -x

This seems like another basic question because I always assumed that if I threw something in my /etc/fstab then it will be automatically mounted at boot time (unless I put in the 'noauto' option). But my NFS partition isn't getting mounted, here's the excerpt from my /etc/fstab file, split on the whitespace so it's easier to read: nfs_server:/exports/var/www /var/www nfs

CentOS 5 updated, Xen host. The portmap on this machine is somehow "stuck" and I can't figure out why. I enabled it to be able to mount a remote nfs share. The first hurdle was that "portmap" didn't appear in the chkconfig list, it was installed with the initial packages but not added to chkconfig. Took me a while to figure this out. Adding and starting it up is no

I am running Redhat 6.1 as a firewall between a cable modem and my home network. Occasionally, I see messages such as these under /var/log/messages: Jan 17 13:38:16 saturn5 portmap[3726]: connect from 24.28.77.200 to dump(): request from unauthorized host Jan 18 14:00:34 saturn5 portmap[1544]: connect from 204.151.148.146 to dump(): request from unauthorized host My assumption is that the

Yesterday I activated SELinux in targeted mode, then I rebooted and started receiving some error messages in the system services initialization: ====================================================================== audit(1156518721.252:2): avc: denied { read } for pid=2223 comm="syslogd" name="libc-2.3.4.so" dev=dm-0 ino=50441 scontext=user_u:system_r:syslogd_t

Hi all I have a CentOS 5.1 server running Xen and recently installed ConfigServer Firewall (CSF) on the main node to give it some protection. On a daily basis I''m getting an email about portmap. haldeamon and xfs consumming too much resources. The main node, dom0 doesn''t even do anything, and everything is done on the domU''s Here''s a thread I''ve

Im trying to install nfs on my server. i tried to do apt-get install nfs nfs-lock portmap. but portmap is the only one available. Is there a new name for nfs and nfs-lock nowadays? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20070815/ad008576/attachment.html>

Greetings I'm running an NIS server that I would very much *not* want to be accessible on some of its interfaces. portmap can be instructed to bind to specific addresses using the -h flag, but this seems to break ypbind. ypbind will attempt to find a server by issuing a broadcast rpc request to the local network. When portmap is not bound to INADDR_ANY, it will not reply to these requests.