Register a SA Forums Account here!
JOINING THE SA FORUMS WILL REMOVE THIS BIG AD, THE ANNOYING UNDERLINED ADS, AND STUPID INTERSTITIAL ADS!!!

You can: log in, read the tech support FAQ, or request your lost password. This dumb message (and those ads) will appear on every screen until you register! Get rid of this crap by registering your own SA Forums Account and joining roughly 150,000 Goons, for the one-time price of $9.95! We charge money because it costs us money per month for bills, and since we don't believe in showing ads to our users, we try to make the money back through forum registrations.
 
  • Post
  • Reply
stealie72
Jan 10, 2007

Their eyes locked and suddenly there was the sound of breaking glass.
\
Sweet. I'll order some memory and learn how to install Ubantu. That was easy.

Adbot
ADBOT LOVES YOU

Longinus00
Dec 29, 2005
Ur-Quan

stealie72 posted:

It's got 512MB, but it's cheap enough to up it to its max supported 2GB. Processor is a AMD Sempron 3600+

Enough to run regular Ubuntu without much difficulty?

I run lubuntu on a old rear end pentium M laptop with 256MB of ram. An even lighter distro might be better but reinstalling is such a pain (it won't boot a USB stick) that I just leave it as it is. With lubuntu 14.04 being an LTS and having 5 years of updates, the laptop will probably break before I have to ever have to do a major upgrade on it again.

Ashex
Jun 25, 2007

These pipes are cleeeean!!!
I've got some really weird behavior with my home file server that started early yesterday. It first presented itself with irssi being super slow (occasionally not responded) and I kept getting server disconnects. I poked around journalctl and found this:


code:
pr 15 22:21:01 gaia.haiti systemd[1]: systemd-journald.service watchdog timeout!
Apr 15 22:22:32 gaia.haiti systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage...
Apr 15 22:22:32 gaia.haiti systemd[1]: systemd-journald.service: main process exited, code=killed, status=10/USR1
Apr 15 22:22:32 gaia.haiti systemd[1]: Unit systemd-journald.service entered failed state.
Apr 15 22:22:32 gaia.haiti systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage...
Apr 15 22:22:32 gaia.haiti systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
Apr 15 22:22:32 gaia.haiti systemd[1]: systemd-journald.service: main process exited, code=killed, status=10/USR1
Apr 15 22:22:32 gaia.haiti systemd[1]: Unit systemd-journald.service entered failed state.
Apr 15 22:22:32 gaia.haiti systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage...
Apr 15 22:22:32 gaia.haiti systemd[1]: systemd-journald.service: main process exited, code=killed, status=10/USR1
Apr 15 22:22:32 gaia.haiti systemd[1]: Unit systemd-journald.service entered failed state.
Apr 15 22:33:52 gaia.haiti systemd-journal[8929]: Forwarding to syslog missed 8 messages.
Apr 15 22:33:53 gaia.haiti systemd-journal[8929]: Journal stopped
Apr 15 22:33:53 gaia.haiti systemd-journal[9057]: Permanent journal is using 1.3G (max allowed 1.3G, trying to leave 11.7M free of 33.9G available → current limit 1.3G).
Apr 15 22:33:53 gaia.haiti systemd-journald[8929]: Received SIGTERM from PID 1 (systemd).
Apr 15 22:33:53 gaia.haiti systemd[1]: Unit systemd-journald.service entered failed state.
Apr 15 22:33:53 gaia.haiti systemd[1]: systemd-journald.service has no holdoff time, scheduling restart.
Apr 15 22:33:53 gaia.haiti systemd[1]: Stopping Journal Service...
Apr 15 22:33:53 gaia.haiti systemd[1]: Starting Journal Service...
Apr 15 22:33:53 gaia.haiti systemd[1]: Started Journal Service.
Apr 15 22:33:53 gaia.haiti systemd-journal[9057]: Journal started
Which looks a little strange but didn't explain the irssi behavior. On a whim I turned up the front fan on the server as I had seen a couple alerts about the disk temp hitting 40C, within a few minutes munin spewed a bunch of alerts, primarily OK alerts around disk latency which is a little strange. That said, I keep getting alerts about eth0 errors being unknown/a high number.

This morning I looked at munin and there are huge gaps in the charts, 1-2 hours which is really strange. Looking in the munin logs I see errors about connecting to the tcp port. Anyone know what's going on? I've got munin configured to use CGI for the graph generation.

Edit: I've just lost network connectivity to the server (ssh/http) for 5-10 minutes, after I got back in I saw the systemd messages above. Scrolling through my buffer I see the following error appeared regularly yesterday:

code:
[1279012.741565] INFO: task nginx:32084 blocked for more than 120 seconds.
[1279012.741616]       Not tainted 3.13.7-1-ARCH #1
[1279012.741648] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[1279012.741701] nginx           D 00000343     0 32084  32083 0x00000000
[1279012.741706]  c0f7fe7c 00200086 c0b4e930 00000343 00000000 c16aca40 2b3cbea6 00048ae4
[1279012.741712]  c16aca40 f4c7c2c0 c0faac80 c0faac80 c0f7fe40 00054878 00000000 c0f7ff14
[1279012.741717]  00000000 00000000 c0b4e930 00000000 c0bfe42c c0bfe490 000005a8 000005a8
[1279012.741722] Call Trace:
[1279012.741731]  [<c1453443>] schedule+0x23/0x60
[1279012.741736]  [<c14537c4>] schedule_preempt_disabled+0x14/0x20
[1279012.741739]  [<c1455725>] __mutex_lock_slowpath+0x105/0x330
[1279012.741742]  [<c1455960>] mutex_lock+0x10/0x1c
[1279012.741747]  [<c1104870>] generic_file_aio_write+0x40/0x90
[1279012.741763]  [<c1156467>] do_sync_write+0x57/0x90
[1279012.741767]  [<c1156410>] ? do_sync_read+0x90/0x90
[1279012.741770]  [<c1156c25>] vfs_write+0x95/0x1c0
[1279012.741773]  [<c11572f1>] SyS_write+0x51/0x90
[1279012.741777]  [<c145d40d>] sysenter_do_call+0x12/0x28
Looking on google suggests this is related to resource starvation.

Ashex fucked around with this message at 08:26 on Apr 16, 2014

Cidrick
Jun 10, 2001

Praise the siamese
That's showing that nginx was stuck waiting for i/o for at least 120 seconds. My guess is that one of your hard drives is probably going south.

Ashex
Jun 25, 2007

These pipes are cleeeean!!!
That doesn't make sense though as I just got this SSD. The OS/nginx are running on there. I did a lot more digging and using the sysstat tools I figured out that I was swapping pretty badly, ended up having to reboot. I need to get a PAE kernel built as I've got 8GB of memory on i686.

I'm not sure why I ran out of memory as normally I'm hovering around 1.5GB.

Ashex fucked around with this message at 15:00 on Apr 16, 2014

Cidrick
Jun 10, 2001

Praise the siamese

Ashex posted:

That doesn't make sense though as I just got this SSD. The OS/nginx are running on there. I did a lot more digging and using the sysstat tools I figured out that I was swapping pretty badly, ended up having to reboot. I need to get a PAE kernel built as I've got 8GB of memory on i686.


Is the SSD the only hard drive in that machine? Is nginx serving up any content that isn't on that hard drive?

What does sar -d show for that time period as far as await and svctime?

evol262
Nov 30, 2010
#!/usr/bin/perl

Ashex posted:

That doesn't make sense though as I just got this SSD. The OS/nginx are running on there. I did a lot more digging and using the sysstat tools I figured out that I was swapping pretty badly, ended up having to reboot. I need to get a PAE kernel built as I've got 8GB of memory on i686.

I'm not sure why I ran out of memory as normally I'm hovering around 1.5GB.

Why is it i686 in 2014?

What is the server actually running? There shouldn't be this much memory pressure on a home file server with no activity.

It looks like you're potentially out of memory and swapping like mad. Or a totally unresponsive disk.

Check with smartmontools?

Ashex
Jun 25, 2007

These pipes are cleeeean!!!
I didn't install sysstat until this morning so I don't have historical data that would be of any use. I've got a raid 6 with six disks in it spread across the motherboard and an expansion card, nginx is only serving content on the SSD.

It's i686 because the server was originally running on an atom board in 2009 and was gradually upgraded to ivy bridge over the course of a few years. I have smartmon (configured to run short/long tests) running in the background and haven't received anything aside from occasional temperature alerts.

Ashex fucked around with this message at 16:26 on Apr 16, 2014

YouTuber
Jul 31, 2004

by FactsAreUseless

stealie72 posted:

Sweet. I'll order some memory and learn how to install Ubantu. That was easy.

I found Ubuntu's Unity interface made older computers run like poo poo. That was with 512mb ram.

stealie72
Jan 10, 2007

Their eyes locked and suddenly there was the sound of breaking glass.
\

YouTuber posted:

I found Ubuntu's Unity interface made older computers run like poo poo. That was with 512mb ram.

Turns out I had a brain fart and forgot that it's got 1GB, not the standard 512mb after actually opening it up. Going to install today and see how it does, and if I need more RAM, it's trivial to upgrade to 2GB. If I'm still not happy, I'll play around with a lightweight version. This isn't a mission critical computer, so I have some freedom to experiment.

edit: I assume as a casual user I want the 12.04 LTS version since I'm not at all after the latest and greatest? I suppose I should have asked that instead of assuming.

stealie72 fucked around with this message at 19:51 on Apr 16, 2014

nescience
Jan 24, 2011

h'okay

stealie72 posted:

Turns out I had a brain fart and forgot that it's got 1GB, not the standard 512mb after actually opening it up. Going to install today and see how it does, and if I need more RAM, it's trivial to upgrade to 2GB. If I'm still not happy, I'll play around with a lightweight version. This isn't a mission critical computer, so I have some freedom to experiment.

edit: I assume as a casual user I want the 12.04 LTS version since I'm not at all after the latest and greatest? I suppose I should have asked that instead of assuming.

In less than 24 hours, Ubuntu 14.04 LTS will be available, if you're sticking to the mainstream Ubuntu flavors, just hold out for a few more hours.
edit: Although, it might be easier to configure/fix problems on 12.04 since it's older, and it will still be supported for a few more years.

I'm having a good time with ElementaryOS. It's essentially a re-skinned version of Ubuntu 12.04LTS with a similar look/shortcuts as a Mac, and it's pretty responsive on my netbook (2009ish Atom, with 1GB of RAM). So if you're up to try something different, I recommend that.




Question with firewall/snmpd. I just installed snmpd on a Debian 7 server, and I'm not able to reach that port from remote machines.

I added these iptable rules on my server

pre:
iptables -A INPUT -p udp -m udp --dport 161 -j ACCEPT
iptables -A OUTPUT -p udp -m udp --sport 161 -j ACCEPT
I confirmed it with
pre:
# netstat -nlpu|grep snmp
udp        0      0 0.0.0.0:161             0.0.0.0:*                           19173/snmpd
and

pre:
# iptables --list
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
ACCEPT     udp  --  anywhere             anywhere             udp dpt:snmp

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
ACCEPT     udp  --  anywhere             anywhere             udp spt:snmp

When I use telnet to ping port 161, it says it's not open. Are there any other iptable rules I'm supposed to add?

edit:
on a related note, are there any web based GUI that makes firewall rules easier to edit? I wouldn't complain if iptables were as easy to configure as the Windows one. I tried out Ajenti, but the firewall CP is even slower to edit than CLI.

nescience fucked around with this message at 20:24 on Apr 16, 2014

fatherdog
Feb 16, 2005

nescience posted:

In less than 24 hours, Ubuntu 14.04 LTS will be available, if you're sticking to the mainstream Ubuntu flavors, just hold out for a few more hours.
edit: Although, it might be easier to configure/fix problems on 12.04 since it's older, and it will still be supported for a few more years.

I'm having a good time with ElementaryOS. It's essentially a re-skinned version of Ubuntu 12.04LTS with a similar look/shortcuts as a Mac, and it's pretty responsive on my netbook (2009ish Atom, with 1GB of RAM). So if you're up to try something different, I recommend that.




Question with firewall/snmpd. I just installed snmpd on a Debian 7 server, and I'm not able to reach that port from remote machines.

I added these iptable rules on my server

pre:
iptables -A INPUT -p udp -m udp --dport 161 -j ACCEPT
iptables -A OUTPUT -p udp -m udp --sport 161 -j ACCEPT
I confirmed it with
pre:
# netstat -nlpu|grep snmp
udp        0      0 0.0.0.0:161             0.0.0.0:*                           19173/snmpd
and

pre:
# iptables --list
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
ACCEPT     udp  --  anywhere             anywhere             udp dpt:snmp

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
ACCEPT     udp  --  anywhere             anywhere             udp spt:snmp

When I use telnet to ping port 161, it says it's not open. Are there any other iptable rules I'm supposed to add?


You allowed udp; telnet uses tcp, regardless of the port you're pointing it at, so naturally it's going to be blocked.

nescience
Jan 24, 2011

h'okay

fatherdog posted:

You allowed udp; telnet uses tcp, regardless of the port you're pointing it at, so naturally it's going to be blocked.

Okay =( I pinged it with UDP and it worked. So now i have to figure out whats wrong with my monitoring software?

Cidrick
Jun 10, 2001

Praise the siamese

fatherdog posted:

You allowed udp; telnet uses tcp, regardless of the port you're pointing it at, so naturally it's going to be blocked.

This. Plus these days everyone should be using netcat anyway

$ nc -vuz host 161

Would accomplish what you're looking for.

nescience
Jan 24, 2011

h'okay

Cidrick posted:

This. Plus these days everyone should be using netcat anyway

$ nc -vuz host 161

Would accomplish what you're looking for.

thanks for this.

I turned off my firewall and my SNMP monitor still won't work, so I'm guessing it's not iptables. I'll keep looking =(

evol262
Nov 30, 2010
#!/usr/bin/perl

nescience posted:

thanks for this.

I turned off my firewall and my SNMP monitor still won't work, so I'm guessing it's not iptables. I'll keep looking =(

Are you trapping? v2 or v3? What's monitoring? Tried snmpwalk-ing OIDs from localhost and externally?

Spatulater bro!
Aug 19, 2003

Punch! Punch! Punch!

What is the recommended program(s) for ripping an audio CD and burning an identical copy without any gaps between tracks? I've burned countless CDs with K3B, and even after removing the 2 second gap setting, I always still get a slight pause between tracks. But now I'm going to start making copies of my CD collection and I definitely do not want those gaps. Are there any settings in the ripping and/or burning process that will help make my copy perfect quality and gapless?

Applebees
Jul 23, 2013

yospos

caiman posted:

What is the recommended program(s) for ripping an audio CD and burning an identical copy without any gaps between tracks? I've burned countless CDs with K3B, and even after removing the 2 second gap setting, I always still get a slight pause between tracks. But now I'm going to start making copies of my CD collection and I definitely do not want those gaps. Are there any settings in the ripping and/or burning process that will help make my copy perfect quality and gapless?

I use cdrdao to make identical copies.

OctaviusBeaver
Apr 30, 2009

Say what now?
So I'm trying to install Ubuntu on a virtual machine while running Windows 7 on the host PC. I am using Virtual PC to run the VM. I downloaded the ISO of Ubuntu 12.04 and mount it on the virtual machine. After a few minutes I get an error saying:

quote:

Ubuntu 12.05 [ 17.691220] microcode: CPU0: update failed for patch_level=0x010000dc

Google is not being very helpful. Anyone have any idea what might be going on or how to fix it?

waffle iron
Jan 16, 2004
microcode is like firmware for a CPU so the processor can be updated. This avoids any future F00F bugs like the original Pentium had. A virtualized CPU doesn't need microcode updates. You can probably ignore it and/or remove the microcode package(s).

Riso
Oct 11, 2008

by merry exmarx
Please don't use Virtual PC it's old as poo poo at this point and MS only use for it is lousy XP Mode. Grab Vmware Player or Virtualbox.

nescience
Jan 24, 2011

h'okay

evol262 posted:

Are you trapping? v2 or v3? What's monitoring? Tried snmpwalk-ing OIDs from localhost and externally?

v2c, I'm using Observium. How do I go about testing what you've mentioned?

telcoM
Mar 21, 2009
Fallen Rib

nescience posted:

v2c, I'm using Observium. How do I go about testing what you've mentioned?

First, you'll need to have the command-line net-snmp tools installed, both on the system you have trouble monitoring, and on the system that is running your monitoring package. Depending on your Linux distribution, they may or may not be in the same package as the snmpd daemon. For example, on Debian, they come with the "snmp" package; on RHEL6, the package name is "net-snmp-utils".

Then, you'll need to know the configured SNMP community name. If you have configured multiple community names, one with read access only is fine. If you haven't configured any community name, try "public".

So, assuming that your community name is "public", run this on the host that runs the snmpd you wish to monitor, to verify that snmpd works:
code:
snmpwalk -v2c -c public 127.0.0.1
You should get multiple lines of response if snmpd works and the community name is valid.

If you get "Timeout: No Response from 127.0.0.1", make sure your snmpd daemon is actually running and your community name is correct.

Then, run the same command on your Observium host, replacing 127.0.0.1 with the IP address with the real IP of the system you wish to monitor. Unless you've done something clever with the access control rules of snmpd, you should get pretty much the same multi-line response as when running the command locally.

If snmpwalk works on localhost but not on the Observium host, something is blocking the SNMP packets between the hosts. Perhaps the Observium host too needs to have its iptables firewall modified to allow SNMP?

Bob Morales
Aug 18, 2006


Just wear the fucking mask, Bob

I don't care how many people I probably infected with COVID-19 while refusing to wear a mask, my comfort is far more important than the health and safety of everyone around me!

YouTuber posted:

I found Ubuntu's Unity interface made older computers run like poo poo. That was with 512mb ram.

The UI in 14.04 feels much smoother than 12.04, at least on my HD3000 machine.

stealie72
Jan 10, 2007

Their eyes locked and suddenly there was the sound of breaking glass.
\
Posting this from chrome in Ubuntu 12.04 on my laptop. Setup has a few kinks due to lovely internet connections and a proprietary wifi driver, but once I got the computer plugged into a LAN, it was trivial.

Still going to upgrade my memory because things are a tiny bit laggy, but overall a HUGE improvement over XP.

If I do decide to eventually upgrade to 14.04, is it like installing a new version of windows, or am I able to just install it over 12.04 and have all my apps and whatnot come along for the ride? I'm assuming it's more like upgrading the OS on a mac than upgrading the OS on windows.

Not surprisingly, Ubuntu reminds me a lot of the version of OSX that I was using until a couple years ago. And I'd forgotten just how awesome it is to be able to go into terminal to diagnose issues and whatnot.

Grumpwagon
May 6, 2007
I am a giant assfuck who needs to harden the fuck up.

stealie72 posted:

Posting this from chrome in Ubuntu 12.04 on my laptop. Setup has a few kinks due to lovely internet connections and a proprietary wifi driver, but once I got the computer plugged into a LAN, it was trivial.

Still going to upgrade my memory because things are a tiny bit laggy, but overall a HUGE improvement over XP.

If I do decide to eventually upgrade to 14.04, is it like installing a new version of windows, or am I able to just install it over 12.04 and have all my apps and whatnot come along for the ride? I'm assuming it's more like upgrading the OS on a mac than upgrading the OS on windows.

Not surprisingly, Ubuntu reminds me a lot of the version of OSX that I was using until a couple years ago. And I'd forgotten just how awesome it is to be able to go into terminal to diagnose issues and whatnot.

Upgrading versions is in theory trivial and non-destructive. I occasionally have had problems in the past where some stuff doesn't work after an upgrade, but the process itself is painless.

KoRMaK
Jul 31, 2012



This is bothering me, I can't figure out what the theme pictured in this screenshot is http://www.noobslab.com/2011/11/system-monitor-applet-for-gnome-shell.html

The colors and the transparency is what I'm most interested in. I'm running ubuntu 12 in my dev environment and would like to theme it to look like that in the screenshot. Does anyone recognize that theme and can supply me with a name?

spankmeister
Jun 15, 2008






KoRMaK posted:

This is bothering me, I can't figure out what the theme pictured in this screenshot is http://www.noobslab.com/2011/11/system-monitor-applet-for-gnome-shell.html

The colors and the transparency is what I'm most interested in. I'm running ubuntu 12 in my dev environment and would like to theme it to look like that in the screenshot. Does anyone recognize that theme and can supply me with a name?

This looks to me like the default theme in Fedora.

Suspicious Dish
Sep 24, 2011

2020 is the year of linux on the desktop, bro
Fun Shoe
That's an old version of the stock GNOME 3 theme. The borders around the panel are gone in newer versions, making the panel melt into the monitor / laptop bezel.

KoRMaK
Jul 31, 2012



Suspicious Dish posted:

That's an old version of the stock GNOME 3 theme. The borders around the panel are gone in newer versions, making the panel melt into the monitor / laptop bezel.
I like the color, transparency, and the border. Are you saying it's not like that anymore?

Suspicious Dish
Sep 24, 2011

2020 is the year of linux on the desktop, bro
Fun Shoe
The only thing that changed is that we removed the tiny white border below the panel. It might take a bit of getting used to, but I think it looks better without it.

Illusive Fuck Man
Jul 5, 2004
RIP John McCain feel better xoxo 💋 🙏
Taco Defender
I'm doing some funky poo poo again, and can't figure out how to get what I want.

I'm connecting to ISCSI targets using open-iscsi, and I want to be able to make sure the device nodes are created with specific names. As things are right now, it just uses the first free letter (/dev/sda, /dev/sdb, etc). Open-iscsi does not seem to have any option for specifying the device name when connecting.

For example, I want to connect to some target 'asdf' at 10.1.0.1 and place the device node at /dev/sdb. Here's dumb poo poo I've done so far:

Idea 1: Create a symlink from /dev/sde to /dev/disk/by-path/ip-10.1.0.1:3260-iscsi-iqn.asdf.org:blah-lun-1 (which is itself a symlink to /dev/sda)

Problems:
If you partition the device, there won't be any symlinks to the partitions.
If I later connect to another device (after /dev/sda has been created and /dev/sdb links to the /dev/disk/by-path/...), open-iscsi (or the scsi kernel module?) tries to create /dev/sdb, but can't. The connection succeeds but no device node is created.

Idea 2: When connecting to a new target, get rid of the nodes it creates automatically, and create my own device nodes with the correct major/minors

Problems:
This kinda works, except that when I fdisk /dev/sdb (Which I have created with major 8 and minor 0) and create a new partition, I end up with a /dev/sda1 instead of /dev/sdb1.

Is this something I can solve with udev rules somehow? I'm starting to get lost.

evol262
Nov 30, 2010
#!/usr/bin/perl

Illusive gently caress Man posted:

I'm doing some funky poo poo again, and can't figure out how to get what I want.

I'm connecting to ISCSI targets using open-iscsi, and I want to be able to make sure the device nodes are created with specific names. As things are right now, it just uses the first free letter (/dev/sda, /dev/sdb, etc). Open-iscsi does not seem to have any option for specifying the device name when connecting.

For example, I want to connect to some target 'asdf' at 10.1.0.1 and place the device node at /dev/sdb. Here's dumb poo poo I've done so far:

Idea 1: Create a symlink from /dev/sde to /dev/disk/by-path/ip-10.1.0.1:3260-iscsi-iqn.asdf.org:blah-lun-1 (which is itself a symlink to /dev/sda)

Problems:
If you partition the device, there won't be any symlinks to the partitions.
If I later connect to another device (after /dev/sda has been created and /dev/sdb links to the /dev/disk/by-path/...), open-iscsi (or the scsi kernel module?) tries to create /dev/sdb, but can't. The connection succeeds but no device node is created.

Idea 2: When connecting to a new target, get rid of the nodes it creates automatically, and create my own device nodes with the correct major/minors

Problems:
This kinda works, except that when I fdisk /dev/sdb (Which I have created with major 8 and minor 0) and create a new partition, I end up with a /dev/sda1 instead of /dev/sdb1.

Is this something I can solve with udev rules somehow? I'm starting to get lost.

Yes, you can do this, but you should not use /dev/sd[anything], and it's generally bad practice versus /dev/disk/by-id, but read on (these still work).

Illusive Fuck Man
Jul 5, 2004
RIP John McCain feel better xoxo 💋 🙏
Taco Defender

evol262 posted:

Yes, you can do this, but you should not use /dev/sd[anything], and it's generally bad practice versus /dev/disk/by-id, but read on (these still work).

Problems with that link: I'd rather not connect, get the ID, set the rule, disconnect, reconnect aaaand... I can't seem to find scsi_id for this system. Probably need to compile it myself. Also, what are IDs for iscsi targets based on?

Illusive Fuck Man fucked around with this message at 22:03 on Apr 17, 2014

evol262
Nov 30, 2010
#!/usr/bin/perl

Illusive gently caress Man posted:

Problems with that link: I'd rather not connect, get the ID, set the rule, disconnect, reconnect aaaand... I can't seem to find scsi_id for this system. Probably need to compile it myself. Also, what are IDs for iscsi targets based on?

WWN, like everything else SCSI.

You'd have to "connect, get the ID, set the rule, disconnect, reconnect aaaand" for any udev rule.

nescience
Jan 24, 2011

h'okay

telcoM posted:

First, you'll need to have the command-line net-snmp tools installed, both on the system you have trouble monitoring, and on the system that is running your monitoring package. Depending on your Linux distribution, they may or may not be in the same package as the snmpd daemon. For example, on Debian, they come with the "snmp" package; on RHEL6, the package name is "net-snmp-utils".

Then, you'll need to know the configured SNMP community name. If you have configured multiple community names, one with read access only is fine. If you haven't configured any community name, try "public".

So, assuming that your community name is "public", run this on the host that runs the snmpd you wish to monitor, to verify that snmpd works:
code:
snmpwalk -v2c -c public 127.0.0.1
You should get multiple lines of response if snmpd works and the community name is valid.

If you get "Timeout: No Response from 127.0.0.1", make sure your snmpd daemon is actually running and your community name is correct.

Then, run the same command on your Observium host, replacing 127.0.0.1 with the IP address with the real IP of the system you wish to monitor. Unless you've done something clever with the access control rules of snmpd, you should get pretty much the same multi-line response as when running the command locally.

If snmpwalk works on localhost but not on the Observium host, something is blocking the SNMP packets between the hosts. Perhaps the Observium host too needs to have its iptables firewall modified to allow SNMP?

I tried this out weird results. I installed and am running snmpd on bost my host and server, when I tried what you said:

Running the commands:
#snmpwalk -v2c -c communityname 127.0.0.1
gets timed out errors on both the host and server

#snmpwalk -v2c -c communityname public_ip_address
gets timed out errors on the server, but I can get feedback on the host (it sees its own snmpd?)

#snmpwalk -v2c -c communityname server_ip_address
gets timed out errors from the host.

code:
#service snmpd status
returns okay on both machines.


i edited my snmpd.conf to listen to all IPs, so I don't think it's filtering out IPs.

I remember reading something about only allowing SNMP to be used on certain interfaces? I'm going to try googling that next when I get back.

evol262
Nov 30, 2010
#!/usr/bin/perl

nescience posted:

I tried this out weird results. I installed and am running snmpd on bost my host and server, when I tried what you said:

Running the commands:
#snmpwalk -v2c -c communityname 127.0.0.1
gets timed out errors on both the host and server

#snmpwalk -v2c -c communityname public_ip_address
gets timed out errors on the server, but I can get feedback on the host (it sees its own snmpd?)

#snmpwalk -v2c -c communityname server_ip_address
gets timed out errors from the host.

code:
#service snmpd status
returns okay on both machines.


i edited my snmpd.conf to listen to all IPs, so I don't think it's filtering out IPs.

I remember reading something about only allowing SNMP to be used on certain interfaces? I'm going to try googling that next when I get back.

Output of:

netstat -anp | grep snmpd
iptables -L

Please.

nescience
Jan 24, 2011

h'okay

evol262 posted:

Output of:

netstat -anp | grep snmpd
iptables -L

Please.

pre:
# netstat -anp | grep snmpd
udp        0      0 0.0.0.0:161             0.0.0.0:*                           25944/snmpd  
pre:
# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         
ACCEPT     udp  --  anywhere             anywhere             udp dpt:snmp

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         
ACCEPT     udp  --  anywhere             anywhere             udp spt:snmp

Cidrick
Jun 10, 2001

Praise the siamese
Not that I'm any help whatsever when it comes to snmpd, but if your default iptables policy on input/output/forward are already ACCEPT, then there's no need to set up a special rule to allow it.

Adbot
ADBOT LOVES YOU

nescience
Jan 24, 2011

h'okay

Cidrick posted:

Not that I'm any help whatsever when it comes to snmpd, but if your default iptables policy on input/output/forward are already ACCEPT, then there's no need to set up a special rule to allow it.

Yeah I don't really have my firewall set. I'm just following a tutorial on a blank VPS.

  • 1
  • 2
  • 3
  • 4
  • 5
  • Post
  • Reply