If you are getting the following error
“Couldn’t create temporary archive name.”
Check if you are out of disk space.
df -h
After freeing up some space, you should be able to continue increasing the disk size
lvextend -l +100%FREE /dev/redhat/root xfs_growfs /dev/redhat/root
There are a couple different options for undeleting files for XFS filesystems.
TestDisk is a great command line recovery tool. Unfortunately, it can be slightly more difficult on systems using XFS compared to EXT4 systems. TestDisk does not support undeleting a file in place on XFS.
You can still recover files using TestDisk, you just need to recover the whole drive and dig through the recovery results to find the files you want.
There is also another utility that can be helpful. xfs_undelete
https://github.com/ianka/xfs_undelete
It allows for a little more flexibility in recovering files. For instance, you can specify to recover the files from the past hour to recover.
Download prerequisites
sudo dnf install tcllib wget https://raw.githubusercontent.com/ianka/xfs_undelete/master/xfs_undelete chmod u+x ./xfs_undelete ./xfs_undelete
Example of running xfs_undelete
./xfs_undelete -t -1hour ./dev/sda2
You will need a different filesystem to save the files to. Otherwise you will receive the following error.
Your output directory is /home/bob/recovery/ That is within the filesystem / you want to recover files from. This isn't feasible as it would overwrite the deleted files you wanted to recover. Please specify the option -o /path/to/output_directory on another (rw mounted) filesystem or run xfs_undelete from within a directory on that filesystem so the recovered files could be written there. They cannot be recovered in place.
It’s not the greatest idea to recover on the system while running. Ideally, shut the system down, plug the drive into another machine as read only, and copy the files off.
You could also boot up in single user mode or a live Linux iso/thumbdrive and mount another recovery drive. Should work for both physical and virtual environments.
Looks like the issue has something to do with net-ssh. There are some other similar errors people were having.
https://github.com/ytti/oxidized/issues/2642
https://github.com/ytti/oxidized/pull/2570
The easy way to resolve the issue is to install oxidized using git.
Make sure rake is installed
sudo dnf install rake or sudo apt install rake
Steps were copied from here. https://github.com/ytti/oxidized#build-from-git
You should be able to copy and paste these commands in the users home directory.
git clone https://github.com/ytti/oxidized.git cd oxidized/ gem install bundler rake install
After it is installed, restart the service
systemctl restart oxidized
Or continue on installing and with LibreNMS
If you are getting the following response when trying to use the yum or dnf command,
This system is not registered with an entitlement server. You can use subscription-manager to register.
Try editing the subscription-manager.conf file, and disable it by changing enable=1 to enable=0
sudo nano /etc/yum/pluginconf.d/subscription-manager.conf
After you may run
yum clean
That should take care of the problem.
These steps should be similar across Red Hat type distros.
Before we proceed, lets stop SNMP
sudo systemctl stop snmpd
First we are going to disable SNMP v1 and v2c
You can manually edit the /etc/snmp/snmpd.conf file and comment out or delete every line starting with com2sec, group, access. Or you can run the following sed commands to change it for you.
sudo sed -i 's/^com2sec/# com2sec/g' /etc/snmp/snmpd.conf
sudo sed -i 's/^group/# group/g' /etc/snmp/snmpd.conf
sudo sed -i 's/^access/# access/g' /etc/snmp/snmpd.conf
https://serverfault.com/questions/376688/how-to-disable-version-1-and-version-2c-in-snmpd
Follow the prompts to create a SNMP v3 user.
sudo net-snmp-create-v3-user -ro -a SHA -x AES
Start SNMP
sudo systemctl start snmpd
You should be good to go.
If you are running a firewall, you will need to allow an exception for SNMP, UDP port 161. You may also need to allow an SELinux exception. Check out the last portion of both these articles.
The following links were helpful in setting things up.
https://doc.powerdns.com/recursor/running.html
https://www.reddit.com/r/linuxadmin/comments/9lc4jl/logging_queries_in_pdnsrecursor/
First we need to find the line that says “disable-syslog” and uncomment/change it to
disable-syslog=no
Next find the line that says “quiet” and uncomment/change it to
quiet=no
Some other lines you may want to check and change
logging-facality=1
loglevel=6
Next we need to modify the Systemd unit file to allow PowerDNS Recursor to log to syslog.
systemctl edit --full pdns-recursor.service
On the ExecStart Line, remove the part that says
--disable-syslog
The resulting line should look something like
[Service]
ExecStart=/usr/sbin/pdns_recursor --socket-dir=%t/pdns-recursor --socket-dir=%t/pdns-recursor --daemon=no --write-pid=no --log-timestamp=no
Save the file.
Edit the rsyslog file
sudo vim /etc/rsyslog.conf
Add the following line
local1.* /var/log/pdns_recursor.log
This should now log all of the PowerDNS Recursor log info to “/var/log/pdns_recursor.log”
Restart the rsyslog and PowerDNS Recursor service
sudo systemctl restart rsyslog sudo systemctl restart pdns-recursor
You should now see DNS request in the log file.
tail /var/log/pdns_recursor.log
They should also show up in the “/var/log/messages”
Not sure why it was giving an error. But to resolve the issue
click on “Software Sources”
On the Network line put http://mirror.centos.org/centos-8/8/BaseOS/x86_64/os/
Should be able to go back to the previous page and select what you want to install.
Started getting the following error while running ./validate.php for LibreNMS
Cannot load Zend OPcache - it was already loaded
Looks like the problem arises out of PHP trying to load two ini files for OPcache. Was trying to enable OPcache for LibreNMS so I created an opcache.ini file and put the settings in it. I missed the default 10-opcache.ini file.
Moving all the settings into the 10-opcache.ini file and deleting the created opcache.ini file resolved the issue for me.
The dig command is apart of the bind-utils package. You can install it with.
sudo yum install bind-utils -y
Now run dig
dig localhost
2023 Update: Recent versions of REHL have completely disabled DES which can cause issues even when using the +ssh-rsa or +ssh-rsa. You can use the following command to enable SHA1, however, upgrading the server would be recommended.
update-crypto-policies --set DEFAULT:SHA1
Reason for it not working is some of the older weaker SSH encryption algorithms have been disabled. You can allow ssh to use it by specifying the following option.
-oHostKeyAlgorithms=+ssh-dss
The whole command would look like
ssh -o HostKeyAlgorithms=+ssh-dss root@192.168.111.4