Getifaddrs linux failed err 11

Getifaddrs linux failed err 11

int getifaddrs(struct ifaddrs **ifap);
void freeifaddrs(struct ifaddrs *ifa);

ОПИСАНИЕ

В поле ifa_next содержится указатель на следующую структуру в списке или NULL, если это последний элемент в списке.

Поле ifa_name указывает на имя интерфейса (заканчивающееся null).

В поле ifa_flags содержатся флаги интерфейса, полученные операцией SIOCGIFFLAGS ioctl(2) (список флагов приведён в netdevice(7)).

Поле ifa_addr указывает на структуру, содержащую адрес интерфейса (для определения формата структуры адреса обратитесь к подполю sa_family). Это поле может содержать указатель null.

Поле ifa_netmask указывает на структуру, содержащую маску сети для ifa_addr (если она используется в адресном семействе). Это поле может содержать указатель null.

В зависимости от наличия флага IFF_BROADCAST или IFF_POINTOPOINT в ifa_flags (может быть установлен какой-то один), в ifa_broadaddr будет содержаться широковещательный адрес ifa_addr (если он используется в адресном семействе) или ifa_dstaddr будет содержать адрес назначения интерфейса типа точка-точка.

Поле ifa_data указывает на буфер, содержащий данные, присущие адресному семейству; это поле может быть равно NULL, если данных для этого интерфейса нет.

Память под структуру данных, возвращаемая getifaddrs(), выделяется динамически и должна освобождаться с помощью freeifaddrs(), когда больше не нужна.

Источник

The Picky SysAdmin

Contact

In case you want to reach out via e-mail: eric((AT))pickysysadmin.ca

Tip jar

Copyright information

This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

Symantec Backup Exec RALUS crashes on CentOS 7

We just deployed our first CentOS 7 machine and are trying to back it up using Backup Exec 2010 R3 and the RALUS agent.

After installing the missing compatibility libraries needed for the RALUS:

the agent installs and starts but once the Media Server connects to it the agent crashes.

Some log digging came up with this from /var/log/messages:

and running the agent in debug mode shows this:

I’ve opened a case with Symantec and their answer was that CentOS isn’t supported and neither is RHEL7.

Anyone else running into this? Have you fixed it?

I found a blog post where someone suggested hex editing the beremote binary which I’d rather not do. Plus our version of the agent is newer than the one he describes in his post: http://blog.redweb.at/2012/08/howto-backupexec-2012-linux-agent-and-kernel-3-0-debian/

6 thoughts on “ Symantec Backup Exec RALUS crashes on CentOS 7 ”

Did you ever find a solution to this? Have the same issue on a new box and came across your post with the same exact issue we have.

No not yet. We’re relying on Snapshots of the VM taken via vSphere and our NetApp Storage.

We did just recently upgrade to Backup Exec 2014. My co-worker told me the RALUS hasn’t been updated since 2012 though so I suspect the same problem exists.

I would try the libbesocket.so patch in that blog post you linked (now dead, try http://preview.tinyurl.com/j2le9ke instead) — the process for finding the place to change in newer versions of the library file is well-described in both the article and the comments there (i.e. find ‘$0x8938’ within the hex dump, find the offset of the nearest ‘jns’ op after that.

If you’ve already got an alternative (i.e. your snapshots) then it shouldn’t present too much risk, and its probably a lot easier to manage than the patched kernel recommended by https://www.veritas.com/support/en_US/article.TECH201095

I should have updated my post. The latest Linux Agent from BE 2014 works fine on CentOS 7.

I’ll double check at work tomorrow but I’m pretty sure that’s what we ended up doing.

Any idea how to put the file back together after objdump?

I do not. I never used the patching method. I just backed up the whole VM until we upgraded to BE2014 and the new RALUS supported CentOS 7

Leave a Reply Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Источник

Remote Agent for Linux (RALUS) crashes immediately after starting when Linux server has kernel version 3.x.

Problem

The Remote Agent for Linux (RALUS) crashes immediately after starting on Linux distributions running kernel version 3.x.

The error below is seen when loading the agent in debug mode (.\beremote —log-console).

Error Message

GetIfAddrs(LINUX): failed err = 11

Cause

Kernel version 3.x

Solution

The current solution is to install the following kernel patch: https://bugzilla.kernel.org/show_bug.cgi?id=33992.

Note: Support for kernel version 3.x was added with the release of Backup Exec 2014. Earlier versions of Backup Exec (prior to 2014) do not support kernel 3.x.

Ubuntu 10.0.4 (kernel 3.1.10)

Debian 6.0.3 (kernel 3.1.10)

Was this content helpful?

Rating submitted. Please provide additional feedback (optional):

You are using Microsoft Internet Explorer!

Article Languages

Translated Content

Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.

Источник

Getifaddrs linux failed err 11

15 авг 2021, 15:33

002e:err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
Setting breakpad minidump AppID = 691450
Steam_SetMinidumpSteamID: Caching Steam ID: 76561200720604776 [API loaded no]
003a:err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
X Error of failed request: GLXBadFBConfig
Major opcode of failed request: 152 (GLX)
Minor opcode of failed request: 0 ()
Serial number of failed request: 327
Current serial number in output stream: 327

Система: Linux Mint 20.2 Uma
DE: MATE 1.24.0

60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics (BYT) v: 4.2 Mesa 21.0.3
direct render: Yes
Audio:
Device-1: Intel Atom Processor Z36xxx/Z37xxx Series High Definition Audio
vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 00:1b.0
Sound Server: ALSA v: k5.4.0-74-generic
Network:
Device-1: Intel Wireless 3160 driver: iwlwifi v: kernel port: 2000
bus ID: 02:00.0
IF: wlp2s0 state: up mac:
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Lenovo driver: r8169 v: kernel port: 1000 bus ID: 03:00.0
IF: enp3s0 state: down mac:
Drives:
Local Storage: total: 465.76 GiB used: 17.70 GiB (3.8%)
ID-1: /dev/sda vendor: Seagate model: ST500LT012-1DG142 size: 465.76 GiB
Partition:
ID-1: / size: 456.96 GiB used: 17.69 GiB (3.9%) fs: ext4 dev: /dev/sda2
Sensors:
System Temperatures: cpu: 55.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 174 Uptime: 14h 22m Memory: 3.73 GiB used: 1.78 GiB (47.9%)
Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17
inxi: 3.0.38

Источник

usbipd cannot open a stub device #128

Comments

nebakanezzer commented Mar 29, 2020

windows server 2016 (server) 192.168.1.21
debian buster (client) 192.168.1.41

C:\Users\Administrator.Violet\Desktop\usbip-win-master>usbip.exe list -l
usbip: error: failed to open usb id database
usbip: error: add_usbdev: invalid hw id: USB\DEVICE_DESCRIPTOR_FAILURE

• busid 1-81 (1c4f:0002)
  unknown vendor : unknown product (1c4f:0002)
• busid 1-189 (03f0:1027)
  unknown vendor : unknown product (03f0:1027)
• busid 1-151 (03f0:1027)
  unknown vendor : unknown product (03f0:1027)
• busid 1-119 (1c4f:0002)
  unknown vendor : unknown product (1c4f:0002)
• busid 1-85 (0658:0200)
  unknown vendor : unknown product (0658:0200)

C:\Users\Administrator.Violet\Desktop\usbip-win-master>usbip.exe bind -b 1-85
usbip: info: bind_device: bind device on busid 1-85: complete

C:\Users\Administrator.Violet\Desktop\usbip-win-master>usbipd.exe -d -4
usbipd: info: starting usbipd (usbip 1.0.0)
usbip: debug: C:\work\usbip-win\userspace\src\usbipd\usbipd_sock.c:38:[build_sockfd] opening 0.0.0.0:3240
usbip: info: listening on 0.0.0.0:3240
usbip: info: connection from 192.168.1.41:60236
usbip: info: recv_pdu: received request: 0x8003 — attach device
usbip: error: get_device_path: traverse_intfdevs failed, returned: 0
usbip: error: open_stub_dev: invalid devno: 85
usbip: error: export_device: cannot open devno: 85
usbip: error: failed to export device: 1-85, err:-1
usbip: info: recv_pdu: request 0x8003: failed

linux client error:

root@Violet-Vm-HA-01:/home/warmachine# usbip attach -r 192.168.1.21 -b 1-85
usbip: error: Attach Request for 1-85 failed — Request Failed

The text was updated successfully, but these errors were encountered:

cezanne commented Mar 30, 2020

@nebakanezzer : Which version did you test ? Binaries in a release page would suffer from your case. But master branch would not.

nebakanezzer commented Mar 30, 2020 •

on the linux client I did a ‘sudo apt-get install usbip’ so not sure what version, I’d have to check

root@Violet-Vm-HA-01:/home/warmachine# apt-cache policy usbip
usbip:
Installed: 2.0+4.19.98-1
Candidate: 2.0+4.19.98-1
Version table:
*** 2.0+4.19.98-1 500
500 http://deb.debian.org/debian buster/main amd64 Packages
100 /var/lib/dpkg/status
2.0+4.19.67-2+deb10u2 500
500 http://security.debian.org/debian-security buster/updates/main amd64 Packages

cezanne commented Mar 31, 2020

Is your master branch ahead of 5e83ddd ?
5e83ddd commit would resolve your case.

nebakanezzer commented Mar 31, 2020 •

583ddd gives me error as well:

C:\Users\Administrator.Violet\Desktop\usbip-win-5e83ddd5224ee343c25eac5c94af571c7981b348>usbip.exe list -l

• busid 1-105 (03f0:1027)
  Hewlett-Packard : Virtual keyboard and mouse (03f0:1027)
• busid 1-85 (0658:0200)
  Sigma Designs, Inc. : unknown product (0658:0200)
• busid 1-202 (0951:1689)
  Kingston Technology : DataTraveler SE9 (0951:1689)

C:\Users\Administrator.Violet\Desktop\usbip-win-5e83ddd5224ee343c25eac5c94af571c7981b348>
C:\Users\Administrator.Violet\Desktop\usbip-win-5e83ddd5224ee343c25eac5c94af571c7981b348>
C:\Users\Administrator.Violet\Desktop\usbip-win-5e83ddd5224ee343c25eac5c94af571c7981b348>usbip.exe bind -b 1-85
usbip: info: bind_device: bind device on busid 1-85: complete

C:\Users\Administrator.Violet\Desktop\usbip-win-5e83ddd5224ee343c25eac5c94af571c7981b348>usbipd.exe -d -4
usbipd: info: starting usbipd (usbip 1.0.0)
usbip: debug: C:\work\usbip-win\userspace\src\usbipd\usbipd_sock.c:38:[build_sockfd] opening 0.0.0.0:3240
usbip: info: listening on 0.0.0.0:3240
usbip: info: connection from 192.168.1.41:37618
usbip: info: recv_pdu: received request: 0x8003 — attach device
usbip: error: get_device_path: traverse_intfdevs failed, returned: 0
usbip: error: open_stub_dev: invalid devno: 85
usbip: error: export_device: cannot open devno: 85
usbip: error: failed to export device: 1-85, err:-1
usbip: info: recv_pdu: request 0x8003: failed

I’ve tried the folders found where the exe’s reside and had similar issues (this appears to be version 0.0.9):

C:\Users\Administrator.Violet\Desktop\usbip-win-0.0.9>usbip.exe list -l

• busid 1-105 (03f0:1027)
  Hewlett-Packard : Virtual keyboard and mouse (03f0:1027)
• busid 1-85 (0658:0200)
  Sigma Designs, Inc. : unknown product (0658:0200)
• busid 1-202 (0951:1689)
  Kingston Technology : DataTraveler SE9 (0951:1689)

C:\Users\Administrator.Violet\Desktop\usbip-win-0.0.9>usbip.exe bind -b 1-85
usbip: info: bind_device: bind device on busid 1-85: complete

C:\Users\Administrator.Violet\Desktop\usbip-win-0.0.9>usbipd.exe -d -4
usbipd: info: starting usbipd (usbip 1.0.0)
usbip: debug: C:\work\usbip-win\userspace\src\usbipd\usbipd_sock.c:38:[build_sockfd] opening 0.0.0.0:3240
usbip: info: listening on 0.0.0.0:3240
usbip: info: connection from 192.168.1.41:37418
usbip: info: recv_pdu: received request: 0x8003 — attach device
usbip: error: get_device_path: traverse_intfdevs failed, returned: 0
usbip: error: open_stub_dev: invalid devno: 85
usbip: error: export_device: cannot open devno: 85
usbip: error: failed to export device: 1-85, err:-1
usbip: info: recv_pdu: request 0x8003: failed

on the linux end, error is always the same:

root@Violet-Vm-HA-01:/home/warmachine# usbip attach -r 192.168.1.21 -b 1-85
usbip: error: Attach Request for 1-85 failed — Request Failed

one thing to note is there are no exe in the 5e83ddd version, so I followed the ‘readme’ to the 009 page for those. should I not be using those? if not, which versions should I be using?

Источник