@dustinb3403 said in Weird question - How often are CentOS packages updated:

@jaredbusch said in Weird question - How often are CentOS packages updated:

@dustinb3403 said in Weird question - How often are CentOS packages updated:

@jaredbusch said in Weird question - How often are CentOS packages updated:

@dustinb3403 said in Weird question - How often are CentOS packages updated:

@stuartjordan said in Weird question - How often are CentOS packages updated:

Don't you want to use a cron so you don't have to check daily?

I have other processes that require manual intervention, so checking only takes a moment.

I would still use yum-cron to do it. Just don't tell it to install if you don't want it to. You will still get the email when things are available.

0_1523897763552_6dab9e40-48dc-4161-a88b-bbdf3011fa5d-image.png

That does seem useful.

No timers to set like needs handled with dnf-automatic just install and edit the conf file.

Installing it and configuring it now...

If you do yes / yes / no it will even have them downloaded for you. not that that is much of an issue generally.

@dustinb3403 said in Need some help with crontab:

Ok and that is what it was.

Simply needed to make a bash script out of it and have it scheduled to run, rather than using the commands directly in cron.

Problem solved.

Solution:

pwd /usr/bin/local touch expiring-alert.sh vi expiring-alert.sh /usr/bin/php /var/www/html/snipeit/artisan snipeit:expiring-alerts sudo vi /etc/crontab 35 * * * 1 <user> /usr/local/bin/expiring-alert.sh

Presumably changing this to be @daily or @weekly would work as well.

MOst of the time that is how I have it setup on my crontab, same for my certbot scripts too.

@dustinb3403 said in Virtualizing Your Cudatel Appliance:

@scottalanmiller said in Virtualizing Your Cudatel Appliance:

Go ahead, download FreePBX and start playing with it. You could have installed it while reading this article!

Any good installation guides here on ML?

@JaredBusch has a great series of posts for FreePBX here.

https://mangolassi.it/topic/11805/freepbx-13-setup-guide

@black3dynamite said in Meltdown Shows Why to Avoid LTS Releases:

What makes Red Hat and SUSE exempt compare to CentOS and OpenSUSE leap? Because we are paying for the support?

Nothing makes them exempt, they ARE CentOS and Leap, just paid for instead of free. They suffer just the same.

@black3dynamite said in Do we dislike Ubuntu:

@nadnerb ElementaryOS is nice but you might not like the idea of not able to save items to your Desktop. Deepin is pretty good too.

Just not on by default. You can enable it...

http://www.fosslinux.com/141/how-to-enable-adding-files-and-folders-to-desktop-in-elementary-os-freya.htm

@scottalanmiller

Yh by accident today I was able to understand it better

2_1518718280839_2018-02-15 20_02_46-Fedora OBR10 - VMware Workstation.png 1_1518718280837_2018-02-15 20_02_41-Fedora OBR10 - VMware Workstation.png 0_1518718280836_2018-02-15 20_08_13-Fedora OBR10 - VMware Workstation.png

Fedora suffers the same fate as centos, and wants to error out but instead when it does not see the boot partitions it will error out quickly then check the next drive, and if it founds it it will update the EFI parition and add another line so it has fail safe method, centos wont do this. so the 1st entry belonged to boot part that was deleted and the 2nd as well, so fedora will keep finding them if you have them and it will auto update the EFI parition while it boots up and adds another line, so then you can boot normally. all this done in the background, you will just see an error fail for boot for 1-2 seconds they you will boot normally cause Fedora already written another entry.

I am starting to like Fedora for servers (minimal install) and if I want centos I can use it as guest vm.

@dustinb3403 said in OpenProject Installation Troubleshooting.:

eh.

I agree, but I just want to see what it's all about, which docker will work fine for. Maybe I'll revisit once I have more time. Doubt I'll be much help even then though.

@lakshmana said in Centos 7.3 Wifi Issue:

@scottalanmiller said in Centos 7.3 Wifi Issue:

@lakshmana said in Centos 7.3 Wifi Issue:

@scottalanmiller Installed Ubuntu now

But OLD Ubuntu, that is expected to have lots of issues because it is not up to date, right?

Yes Now WiFi Detected will go with KVM and then Centos will run it

Great!

@scottalanmiller Thanks Scott it worked

@stacksofplates said in Centos 7.3 Installed:

@lakshmana said in Centos 7.3 Installed:

@scottalanmiller said in Centos 7.3 Installed:

@stacksofplates said in Centos 7.3 Installed:

@lakshmana said in Centos 7.3 Installed:

@stacksofplates for acpi "command not found" is the error

You'll have to install it.

yum install acpi

The package has one more letter in the name. Should be this...

yum install acpid

Then you can fire it up like this...

systemctl start acpid systemctl enable acpid

Installation done but error comes
[root@localhost ~]# sysctl start acpid
sysctl: cannot stat /proc/sys/start: No such file or directory
sysctl: cannot stat /proc/sys/acpid: No such file or directory
[root@localhost ~]# sysctl enable acpid
sysctl: cannot stat /proc/sys/enable: No such file or directory
sysctl: cannot stat /proc/sys/acpid: No such file or directory
[root@localhost ~]#

It's systemctl not sysctl. Two different things.

Thanks

@mikah67 Glad that it is working!

As a general rule, just do a yum -y update before starting an installation to make sure you are fully updated, regardless of which CentOS 7 version you started with.

Ya I also pretty much use Virt-Manager/Virsh. I have a bare KVM server and an OpenStack box. I pretty much use Ansible/Terraform to spin up new instances on OpenStack.

After asking the Wazuh employee I had been speaking to about Kibana 5.6.3, the GitHub repo was updated to include it.

Has potential, has anyone played with it in any way yet?

@stacksofplates said in Newb question - Running a script from the root directory:

@dustinb3403 said in Newb question - Running a script from the root directory:

@stacksofplates said in Newb question - Running a script from the root directory:

@dustinb3403 said in Newb question - Running a script from the root directory:

@stacksofplates said in Newb question - Running a script from the root directory:

@dustinb3403 said in Newb question - Running a script from the root directory:

@stacksofplates said in Newb question - Running a script from the root directory:

@dustinb3403 said in Newb question - Running a script from the root directory:

@scottalanmiller said in Newb question - Running a script from the root directory:

@dustinb3403 said in Newb question - Running a script from the root directory:

@stacksofplates said in Newb question - Running a script from the root directory:

@dustinb3403 said in Newb question - Running a script from the root directory:

@danp said in Newb question - Running a script from the root directory:

Is the directory in your path? What do you get from echo $PATH?

echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/root/opt/scripts/:/root/opt/scripts

I've added it (twice).

Well first off you had /root/opt/scripts not /opt/scripts. Second you either have to log out and back in or tell your user to use the new path with something like

source ~/.bash_profile

I used ````~/opt/scripts``` initially, as I wasn't aware of just adding my scripts into one of the existing locations. (everything said just add a new directory).

By simply moving the script into an already existing path, I am able to update with just "script.sh".

When you are root and your home is /root and you put ~/opt/scripts that is /root/opt/scripts.

Remember that ~ is a shortcut to your home directory, which is /root

So by adding ```/opt/scripts/```` this would've worked, but would've added complexity for no reason.

No that still isn’t a default location. In the OP you said you put the script in /opt/scripts. Where did you actually put it?

Originally I created the directory /opt/scripts and put the script in there so the Directory looks like

/opt/scripts/script.sh

I went back and change the script location to be in /usr/local/bin

So in /usr/local/bin I now have script.sh

This now works without issue, and /opt/scripts no longer exists.

Ok ya that’s where the problem was. /opt/scripts is different than /root/opt/scripts. If you would have had that in your .bashrc or .bash_profile (or whichever shellconfigure you’re using) it would have worked. But you still have to let the user know of the PATH change.

I'm the user in this case, but I never really create / save my own scripts. I just got tired of running a set of commands, every other day.

Thus the need to figure out how I could run the script, without having to jump into the exact directory from which the script was saved.

I mean you have to let the user you are logged in as Know if the change. Either by logging out and back in or by temporarily sourcing the config.

I've logged out, what do you mean "sourcing the config" ?

If you change your PATH while you’re logged on the user account doesn’t know of that change. You have to either log out and log in again or temporarily do something like

source ~/.bashrc

Or the non-aliased version...

@dustinb3403 said in dhclient preventing network.service from starting:

Disabled network manager and the issue appears to be resolved. @Romo thanks for the help.

After all these years, it's still a pain in the neck.

@dashrender
It's a one off issue we have. We have all 50+ Sites running of an MPLS, if something happens and we need BT to look at a line issue then we are subject to OpenReach SLA's. So while they are down most stores have monitored CCTV on a separate BB line, so we use this as a temp VPN connection to a Draytek here that is on a different sub net range to my VM infrastructure. So when they are using the VPN and the route has been changed on the Core switch zabbix can't ping the MPLS Cisco router as the route now goes through the Draytek. So I need to static the route through the MPLS router so zabbix tells me the connection is up once BT have visited.

Just installed on CentOS 7.6 with XFS. Still flawless install.