I have a network emulation with Zabbix server, pc-1 with Zabbix-Agent and pc-2 with SNMPv3 Agent in VirtualBox.
With this discovery rule and action Zabbix easily discovers Agent on pc-1 and adds it to the hosts.
I tried to make Zabbix to discover SNMPv3 Agent (pc-2). SNMP and all that needed is installed on both sides.
With this command from Zabbix server:
snmpget -u <username> -l authPriv -a MD5 -x DES -A <password> -X <password> 192.168.2.1 1.3.6.1.2.1.1.1.0
I get:
SNMPv2-MIB::sysDescr.0 = STRING: Linux pc2 4.4.0-92-generic #115-Ubuntu SMP Thu Aug 10 09:04:33 UTC 2017 x86_64
But discovery rule and action don't work and Zabbix isn't adding 192.168.2.1 as host.
Here are discovery rule with action for SNMPv3 Agent:
Maybe I missed something? There are no normal manuals for this. Thanks for help!
The discovery range used is very large - the discovery is likely just slow and might work if a narrow, targeted range is specified.
Related
I am currently working on the ARM Cortex-M4 inside the NXP i.MX8M Mini.
I am able to compile a project for M4 on Eclipse IDE on an Ubuntu VM.
I would now like to debug on the M4 via a SEGGER Flasher ARM probe, still from Ubuntu.
My probe is well recognized by Ubuntu, and I can launch the J-Link GDB server by simply typing the command :
$ sudo ./JLinkGDBServerCLExe
However, if I type the same command without sudo, I get :
$ ./JLinkGDBServerCLExe
SEGGER J-Link GDB Server V7.58b Command Line Version
JLinkARM.dll V7.58b (DLL compiled Nov 16 2021 15:04:27)
-----GDB Server start settings-----
GDBInit file: none
GDB Server Listening port: 2331
SWO raw output listening port: 2332
Terminal I/O port: 2333
Accept remote connection: yes
Generate logfile: off
Verify download: off
Init regs on start: off
Silent mode: off
Single run mode: off
Target connection timeout: 0 ms
------J-Link related settings------
J-Link Host interface: USB
J-Link script: none
J-Link settings file: none
------Target related settings------
Target device: Unspecified
Target interface: JTAG
Target interface speed: 4000kHz
Target endian: little
Connecting to J-Link...
Connecting to J-Link failed. Connected correctly?
GDBServer will be closed...
Shutting down...
Could not connect to J-Link.
Please check power, connection and settings.
My problem is that when I start eclipse, I get the same result as starting the GDB server without sudo.
It seems that this is a rights issue, how can I solve it?
As #KamilCuk said, the problem came from the udev rules.
So you just have to copy the rules provided by Segger with J-Link Software on the system:
$ sudo cp 99-jlink.rules /etc/udev/rules.d
Then you have to reboot the system:
$ reboot
I've been trying to troubleshoot this problem for some days now.
A couple of minutes after starting an SSH connection to my Namecheap server (on Mac/windows/cPanel's "Terminal"), it crashes and give the following error message :
Error: The connection to the server ended in failure at {TIME} PM. (SIGKILL)
and :
Exit Code: 137
I've tried to create some kind of log file for any SIGKILL signal, but, it seems like none can be made on a Namecheap server :
auditctl doesn't exist,
We can't get systemtap because no package managers are available.
Precision :
uname -a : Linux [-n] 2.6.32-954.3.5.lve1.4.78.el6.x86_64 #1 SMP Thu Mar 26 08:20:27 EDT 2020 x86_64 x86_64 x86_64 GNU/Linux
I calculated the time between each crash : around 6min.
I don't have a very good knowledge of Linux servers, and maybe didn't include needed information. So please ask for any specificities!
Steps I tried
I am trying to setup a Wireguard client on a Raspberry pi
This is the configuration on used
# /etc/wireguard/wg0-client.conf
[Interface]
Address = 10.10.0.4/32
Address = fd86:ea04:1111::4/128
SaveConfig = true
PrivateKey = CLIENT-PRIVATE-KEY
DNS = 8.8.8.8
[Peer]
PublicKey = SERVER-PUBLIC-KEY
Endpoint = SERVER-PUBLIC-IP:PORT
AllowedIPs = 0.0.0.0/0, ::/0
After setup the Wireguard config, I run the sudo wg-quick up wg0-client, it fails like this
pi#raspberrypi:~ $ sudo wg-quick up wg0-client
[#] ip link add wg0-client type wireguard
RTNETLINK answers: Operation not supported
Unable to access interface: Protocol not supported
[#] ip link delete dev wg0-client
Cannot find device "wg0-client"
the Wireguard server side has been working for a while with other devices, so I do not paste the info here
OS and hardware context
/etc/os-release info
pi#raspberrypi:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
/sys/firmware/devicetree/base/model for hardware info
Raspberry Pi 3 Model B Rev 1.2
I solved this the other day for my Pi-2 by removing Wireguard updating/upgrading the Kernel to the latest version, installing the Kernel headers, and reinstalling Wireguard. Worked like a charm after that.
But, you may only need the kernel headers.
You can try doing "sudo apt-get install raspberrypi-kernel-headers" before anything else.
I'm on:
Linux raspberrypi 4.19.118-v7+ #1311 SMP Mon Apr 27 14:21:24 BST 2020 armv7l GNU/Linux
I upgraded my Linux kernel and dovecot failed to start with the following error messages:
Error: service(managesieve-login): listen(*, 4190) failed: Address already in use
Error: service(pop3-login): listen(*, 110) failed: Address already in use
Error: service(pop3-login): listen(*, 995) failed: Address already in use
Error: service(imap-login): listen(*, 143) failed: Address already in use
Error: service(imap-login): listen(*, 993) failed: Address already in use
Fatal: Failed to start listeners
Strangely enough, I couldn't find any process bounded to those port numbers. All commands below return nothing.
# netstat -tulpn | grep 110
# ss -tulpn |grep 110
# fuser 110/tcp
# lsof -i :110
I also tried to change the listen setting to my specific IP address and it still failed the same way.
Any idea how I can solve this problem? Here's my version info:
# uname -a
Linux ip-172-31-26-222 4.14.177-107.254.amzn1.x86_64 #1 SMP Thu May 7 18:30:14 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
# dovecot --version
2.2.36 (1f10bfa63)
Hi it looks like you are using AWS as I am. I recently updated via Yum as well. I noticed that a new package named 'portreserve' was also installed. I killed that process, left the /etc/dovecot/dovecot.conf as it was before and then started Dovecot successfully. I was also immediately able to reconnect my mail clients connection. I hope that helps you.
I also restarted the portreserve program since it seems useful to limit port access.
OS: Red Hat 4.1.2-54
Linux 2.6.18-92.el5 #1 SMP Tue Jun 10 18:49:47 EDT 2008 i686 i686 i386 GNU/Linux
Progress OpenEdge Database Release 10.2B on Linux 32 bit
ODBC Driver: pgoe1023.so (which was available with the database package)
export LD_LIBRARY_PATH=/usr/dlc/odbc/lib:/usr/dlc/lib
export ODBCINI=/etc/odbc.ini
isql -v Progress
I am receiving "Segmentation fault" error when trying to use ODBC connection to progress database using isql command.
I have followed the required steps mentioned in this article and installed missing library libstdc++-libc6.2-2.so.3 (with yum install compat-libstdc++-296.i386).
How can I fix it?
I do not see any indication in the kbase article, nor in your post, that a db is running and accepting SQL connections. The kbase is assuming "testdb", port 5555 and a user named "sysprogress" (password "sysprogress" too).
Assuming that you have a "testdb" and that you setup the user you also need to start a server to accept SQL connections. For instance:
proserve testdb -m3 -Ma 5 -Mpb 5 -S 5555 -ServerType SQL -minport 9000 -maxport 9100
Before you try to use it with your isql stuff you can test that this is working with Progress' "sqlexp" command:
sqlexp -user sysprogress -password sysprogress -db testdb -S 5555
If that doesn't work then you have not correctly configured the db to accept SQL connections and downstream utilities, like isql, will not work.