Red Alert 3 Linux

[Ellyn Krucke]

Thishappens to me more than I'd like to admit, but sometimes I don't notice the power getting low since it only shows up in my status bar, then the computer just quits. I'd like a big alert that warns me before this happens. Is there any way for it to alert me? Ubuntu has a nice popup that tells you it's getting low.

re: hdgarrood 's answer, setting cron to run notify-send actually turned out to be painfully finicky. (I think crontab -e does persist across reboots by default, fortunately). I followed several guides, I'm not sure what exactly fixed it in the end, but here is my full setup for running the checker every 5 minutes:

Instead of zenity you could instead use xmessage (on really spartan machine) or even something like aplay -q /usr/lib/libreoffice/share/gallery/sounds/cow.wav for audio notifications (which have advantage that it will won't interrupt your keyboard typing, and will work even for multi-user laptops with multiple sessions, where DISPLAY=:0 hack would fail)

I had that same problem and I figured out a workaround. I installed from Linux Mint repositories an app called GKrellM. It monitors lots of stuff on your machine and there is battery. Setup with alarms, it works for me like a charm.

The issue is related at KDE environment. I have the same problem with MintMAYA KDE_version. When I worked with Mint9_Gnome a very useful pop-up appeared when a certain level of low-power was reached (auto-configured out_of_the_box on fresh installs). Very very annoying being shutted down without advice and no help founded even googling a lot :(

I'm using KDE but you can use it with every desktop environment. You don't have to run this as root user or go crazy with crontab syntax.You need only to change the notification sound if you want a sound alert. If you wan't to start the script automatically when the desktop environment starts put the script in $USER/bin folder with the BatteryAlertLauncher.sh script:

As I don't have Gnome Shell or Cinnamon installed, I cannot be of direct help as accessing the source could would be much practical since it's rather easy adding such a rudimentary extension with JavaScript.

Hello. I had to move my entire old Splunk directory to a new filesystem for archiving as it was pretty hosed. Did a reinstall back to /opt/splunk and have just been setting it all up again. I created some pretty specific alerts previously that I would like to see if I can just copy over from the old instance. Does anyone know where those are stored?

I'm trying to change the default Alert Sound on GNOME, but I'm not sure how to do this. I've tried to import .ogg files into .local/share/sounds but when I looked at Tweaks nothing changed. Same applies with the Sound setting in Settings. I tried to put the .ogg file in /usr/share/sounds in another Linux Distro, but it's the same result, but I didn't do it on this Distro.

The sounds folder in

/usr/share/gnome-control-center/sounds/gnome-sounds-default.xml

doesn't exist. Same goes for the file. If I create the file manually then it doesn't do anything, I've tried doing this exact same thing on Fedora.

A work around.

I just replaced a sound from /usr/share/sounds/gnome/default/alerts/ with the sound I wanted renaming it to whatever I am replacing it with. Then switched to that sound in Gnome sound settings.

Under Linux, what's a simple way to automatically watch a logfile, and email me if a certain string appears? I have an application that will log certain failures to a logfile, but has no built-in way of sending alerts or executing scripts on failure. I suppose I could rig something up with tail -f and some shell scripts, but I'd rather use an existing maintained tool if it exists.

Those other systems are great for dealing with existing system logs, or with software where you don't have control over the output. I just didn't want to write a bunch of code to do email notifications just yet. So I just created a swatch file like this:

Before we went to a heavyweight solution (Zenoss) we used to use logcheck which is a part of Debian but can easily be ported to other distros as well. I was using it on Gentoo. Distros like RHEL come with logwatch, which does something similar.

I know, hacking a shell script is fun, but way less stable than a mature program being developed for years. Plus, if in the future you need to extend your script or add more triggers, it becomes way more complicated. OSSEC (and other tools) have this framework done for you.

I found a tool called tenshi that appears to do exactly what I need it to do. It's included in the default Debian repos which is nice, unfortunately not in the RHEL/CentOS ones (I have a mix of both OS's as servers).

I know an answer has already been accepted but rsyslog is much more robust and has built-in filtering, SMTP alerts, and non-syslog based file-watching abilities for applications that do not use syslog. It's now the standard syslog implementation on Ubuntu 10.x.

The Alertmanager handles alertssent by client applications such as the Prometheus server.It takes care of deduplicating, grouping, and routingthem to the correct receiver integration such as email, PagerDuty, or OpsGenie.It also takes care of silencing and inhibition of alerts.

Grouping categorizes alerts of similar nature into a single notification. Thisis especially useful during larger outages when many systems fail at once andhundreds to thousands of alerts may be firing simultaneously.

Example: Dozens or hundreds of instances of a service are running in yourcluster when a network partition occurs. Half of your service instancescan no longer reach the database.Alerting rules in Prometheus were configured to send an alert for each serviceinstance if it cannot communicate with the database. As a result hundreds ofalerts are sent to Alertmanager.

As a user, one only wants to get a single page while still being able to seeexactly which service instances were affected. Thus one can configureAlertmanager to group alerts by their cluster and alertname so it sends asingle compact notification.

Example: An alert is firing that informs that an entire cluster is notreachable. Alertmanager can be configured to mute all other alerts concerningthis cluster if that particular alert is firing.This prevents notifications for hundreds or thousands of firing alerts thatare unrelated to the actual issue.

Silences are a straightforward way to simply mute alerts for a given time.A silence is configured based on matchers, just like the routing tree. Incomingalerts are checked whether they match all the equality or regular expressionmatchers of an active silence.If they do, no notifications will be sent out for that alert.

Also looking for a solution like this. Its so easy to set automatic restarts for services in windows servers but no feature like this for Linux. You would think this would be a built in feature by now.

This is a very old post that I wrote that talks about how it could be done. Basically kicking off a custom script via the Alert Engine to do it. This was only for a proof of concept, and it isn't very polished, but it did work.

However, if I had to do it again I'd probably skip the Alert Engine and simply use a SAM Application Template with a Linux Script Monitor (since you already have to have an Application Template for your Process monitors). Have an extra monitor in that template that runs a script that monitors the deamons I want up, and if they are stopped to restart them. Build in some type of logic to handle too many restart attempts, etc. If the deamons are all up, then have the script simply output something to signify everything is ok. The pros to this approach, is that it keeps the ssh creds more secure AND will use the Linux Agent to execute the script if it is deployed.

I got to where I do this for all of my custom script monitors. Why just monitor and create alerts when I'm already in here writing code that will execute on the target machine. If the condition fails i write an output that will set the component into Warning and so SAM records that i've initiated a remediation, and if that remediation fails then we actually mark the component as down and we know that whatever is wrong is more complex than my existing automatic fix can handle.

Hi,

I got a critical alert from a Linux agent and after I fixed the problem I went to checkmk to clear the log so the alert will go away. To my surprise, for the Linux agent there is no Open Log > Clear option like for the Windows one.

I tried by acknowledging the problem but the alert is still there after 24 hours.

So i started to use VirtualBox in windows 10 and i would like to know if those alert from my windows 10 security program (avast antivirus), during my installation/upgrading of TheHarvester program at virtualmachine Kali Linux of VirtualBox will cause any threat or harm to my personal computer? ( I am really concerned about the others getting chance hacking into my pc XD )

Kali Linux contains a ton of malicious tools, so it's expected that antivirus software complains about them. This can happen if it scans the network traffic during upgrade, which is probably the case now, as the upgrade uses plain HTTP connections. Some antivirus software might also scan the disk images of virtual machines. Both may cause problems to or break your Kali installation, so it might be a good idea to add some exceptions.

Despite technically malware, these aren't a security problem per se, but they are powerful tools that may cause problems if you don't use them wisely. You might end up weakening your security if you attack against your host machine.

To see if Snort is working, beyond just getting it to load without errors (not a trivial feat in itself), it is helpful to generate some alerts. The easiest way to do this to validate setup and configuration is to create a couple of testing rules, load them in Snort, and trigger them so you can check to see if they generate alerts as expected. Put your testing rules in the local.rules file that is located in the /etc/snort/rules directory.

3a8082e126