Tag Info

Hot answers tagged

4

Under "normal/common" circumstances (for example, when you're running a "normal" server, that, as far as you know, should NOT be running and should not have installed any kind of "hostile" software), all the software components used/usable for hostile activities tries to escape any kind of detection. So, as a first rule, it's generally not possible to ...


3

This depends on how you provide the repo config through puppet. Do you place a file under /etc/yum/repos.d or a custom provider? You could take measures to make sure that the /etc/yum.repos.d/ dir is purged (ie kept free from files not provided by puppet), check the file resource in the puppet type reference for details. Problem with this approach is that ...


2

Here is my fork: Reduce size of image from 3.8G to 825MB Database initialization moved out of the image build phase Now database initializes at the containeer startup with no database files mounted Media reuse support outside of container Added graceful shutdown on container stop Removed sshd You may check here: ...


2

HP ProLiant server hardware evolves throughout the lifecycles of long-running Operating System distributions like Red Hat Enterprise Linux. In your original post, I specifically asked what version of RHEL you were attempting to install. This is important information because Red Hat 6 was introduced well before Generation 8 ProLiant servers. There are ...


1

From this thread (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/618542): I found an answer to the ERROR: (0x03:0x0101): Invalid command opcode:opcode=0x85 problem: http://kb.lsi.com/Print16532.aspx : "This error can be safely ignored." What is happening is that the kernel is sending a scsi code 0x85 (which from ...


1

So found this in my digging, Unfortunately, this is a known bug on RHEL/CentOS 6.5 AMIs, however there are two workarounds to extend the file system as you requested: You can mount the volume to another instance and use parted to expand the partition boundary for the volume that the root FS is on as mentioned at the below link: ...


1

You have two options for getting a newer version of gcc than the one shipped with RHEL 6, your current Linux distribution. Upgrade to RHEL 7, which shipped with gcc 4.8.2. Use the Red Hat Developer Toolset, a software collection which supplies gcc 4.9.1 and updated versions of related tools, on either RHEL 6 or RHEL 7. This software collection is available ...


1

If the attack is over and your VPS is not participating in it anymore, you can't tell. If it is still ongoing you can check it via tcpdump. You could search your system for stuff you didn't put there, but otherwise you are out of luck.


1

Had the same error on my server: > service httpd status httpd dead but subsys locked Found, that the directory /var/run/httpd was NOT readable/executable by world: drwx------ 2 root apache 4096 Apr 23 14:15 /var/run/httpd Therefore any user (beside root) could not examine the pidfile (which did exist)! The httpd-Process was already running ...


1

Instead of doing it manually, like suggested in the other answers, you could also change the init script. Just add such a line to the header: # chkconfig: 35 90 10 This will instruct chkconfig to add the service to the runlevels 3 and 5, with a start position of 90 and a kill position of 10.


1

I changed the following option in my *.vmx file: mem.hotadd = "FALSE" By default it is set to "TRUE". I've not seen any issues changing it... I don't have any CentOS VMs running on MS Hyper-V so, dig in and see what options are available to fix this issue.


1

I worked this out after reading dsmsk80 answer and looking in the ifup-eth script. The key line is this: /sbin/arping -c 2 -w 3 -D -I <INTERFACE> <VLAN> So for the OP example: /sbin/arping -c 2 -w 3 -D -I eth0:1 192.168.0.2 Something I used this on recently returned this: > /sbin/arping -c 2 -w 3 -D -I eth0.1508 192.168.8.1 ...


1

Ok, I found this little bug, I knew it was something small enough to not be noticed. It turns out the PATH variable was being changed when the scripts in cron were ran and ended up like this /usr/bin:/bin. The conflicting date command was installed in /usr/bin and not in /bin so cron was using the wrong one and I couldn't notice because in the normal user ...


1

To display the current value of a specific cluster property, use the following command. pcs property list --all To display the current value of a specific cluster property, use the following command. pcs property show property To set the value of a cluster property, use the following pcs command. pcs property set property=value


1

You can set the value of resource-stickiness, a resource meta option that indicates how much the resource prefers to stay where it is (the default value is 0) for a given resource or group whith the following command: # pcs resource meta resource_id resource-stickiness=100 For example: # pcs resource meta dns_ip resource-stickiness=100 # pcs ...



Only top voted, non community-wiki answers of a minimum length are eligible