[Mondo-devel] Mondo Archive v3.2.2-r3578: ASSERTION FAILED: `call[0]!='\0''

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[Mondo-devel] Mondo Archive v3.2.2-r3578: ASSERTION FAILED: `call[0]!='\0''

spezialist
Hi all!

I found here such error on CentOS-6.7 when using an option -n (mondoarchive tries to mount automatically a NFS resource from /etc/fstab):

==================================================
# mondoarchive -K 10 -O -p snmpproxy-kv0 -n nfs://10.3.33.100:/export/DCIM_backups -d /snmpproxy-kv0.back/BMR -E "/data/tmp/mondo|/mnt/nfs_backups" -T /data/tmp/mondo -S /data/tmp/mondo -F -s 4480m -6z
See /var/log/mondoarchive.log for details of backup run.
Checking sanity of your Linux distribution
Done.
Network share 10.3.33.100:/export/DCIM_backups is not mounted. Trying to mount i
ASSERTION FAILED: `call[0]!='\0''
        at libmondo-fork.c:53 in call_program_and_get_last_line_of_output

(I)gnore, ignore (A)ll, (D)ebug, a(B)ort, or (E)xit? d
(Unknown) signal received from OS
(Unknown)
Fatal error... MondoRescue is terminating in response to a signal from the OS
---FATALERROR--- MondoRescue is terminating in response to a signal from the OS
If you require technical support, please contact the mailing list.
See http://www.mondorescue.org for details.
The list's members can help you, if you attach that file to your e-mail.
Log file: /var/log/mondoarchive.log
Mondo has aborted.
Execution run ended; result=254
Type 'less /var/log/mondoarchive.log' to see the output log
==================================================

Interestingly, but despite this error, mondoarchive actually normally mounted the specified NFS resource. Besides, manually this NFS resource is also mounted without errors:

==================================================
# mount -vvvvvvvvvvvvvvvvv 10.3.33.100:/export/DCIM_backups
mount: fstab path: "/etc/fstab"
mount: mtab path:  "/etc/mtab"
mount: lock path:  "/etc/mtab~"
mount: temp path:  "/etc/mtab.tmp"
mount: UID:        0
mount: eUID:       0
mount: spec:  "10.3.33.100:/export/DCIM_backups"
mount: node:  "/mnt/nfs_backups"
mount: types: "nfs"
mount: opts:  "noauto,noatime,nolock,mountproto=tcp"
final mount options: 'nolock,mountproto=tcp'
mount: external mount: argv[0] = "/sbin/mount.nfs"
mount: external mount: argv[1] = "10.3.33.100:/export/DCIM_backups"
mount: external mount: argv[2] = "/mnt/nfs_backups"
mount: external mount: argv[3] = "-v"
mount: external mount: argv[4] = "-o"
mount: external mount: argv[5] = "rw,noauto,noatime,nolock,mountproto=tcp"
mount.nfs: timeout set for Thu May 19 11:54:23 2016
mount.nfs: trying text-based options 'nolock,mountproto=tcp,addr=10.3.33.100,mountaddr=10.3.33.100'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 10.3.33.100 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=6
mount.nfs: trying 10.3.33.100 prog 100005 vers 3 prot TCP port 32770
10.3.33.100:/export/DCIM_backups on /mnt/nfs_backups type nfs (rw,noauto,noatime,nolock,mountproto=tcp)

# cd /mnt/nfs_backups/snmpproxy-kv0.back/BMR; pwd
/mnt/nfs_backups/snmpproxy-kv0.back/BMR

# umount -vvvvvvvvvvvvvvvvv 10.3.33.100:/export/DCIM_backups
Trying to umount 10.3.33.100:/export/DCIM_backups
Legacy NFS mount point detected
umount.nfs: prog 100005, trying vers=3, prot=6
umount.nfs: trying 10.3.33.100 prog 100005 vers 3 prot TCP port 32770
10.3.33.100:/export/DCIM_backups umounted
==================================================

I send a log file in attachment.

Besides, it is possible to see one more bug: in spite of the fact that in command line the tmpdir and scratchdir is /data/tmp/mondo is specified, mondoarchive uses the standard directory /tmp (see a log file).

Very thanks for the support.

--
Чорнобиль форева!

-- реклама -----------------------------------------------------------
Старт продаж ЖК "Новая Англия"! Цена от 14 900 грн/кв.м!
http://h.holder.com.ua/c?tz&z1585&b117887&s03908&r[rndID]&u
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
Mondo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mondo-devel

mondoarchive.log (14K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [Mondo-devel] Mondo Archive v3.2.2-r3578: ASSERTION FAILED: `call[0]!='\0''

Bruno Cornec-4
Hello,

spezialist said on Thu, May 19, 2016 at 12:20:09PM +0300:
>I found here such error on CentOS-6.7 when using an option -n (mondoarchive tries to mount automatically a NFS resource from /etc/fstab):

Yep, agreed :-(

>==================================================
>Network share 10.3.33.100:/export/DCIM_backups is not mounted. Trying to mount i
>ASSERTION FAILED: `call[0]!='\0''
>        at libmondo-fork.c:53 in call_program_and_get_last_line_of_output

There was an error indeed in a variable used. I should have fixed it in a first beta for 3.2.2 under ftp://ftp.mondorescue.org/test/rhel/6/x86_64
Let me know if that improves stuff for you.

>Besides, it is possible to see one more bug: in spite of the fact that in command line the tmpdir and scratchdir is /data/tmp/mondo is specified, mondoarchive uses the standard directory /tmp (see a log file).

This is not a bug, but a feature.
At the start, before any command line parameter analysis, mondoarchive needs to create temp files. So for that it uses the TMPDIR variable (or other look at man page) or /tmp in case none is declared. Later on, it will use the one you precise.

Bruno.
--
Open Source Profession, WW Linux Community Lead  http://www.hpintelco.net
HPE EMEA EG Open Source Technology Strategist http://hp.com/go/opensource
FLOSS projects:     http://mondorescue.org     http://project-builder.org
Musique ancienne? http://www.musique-ancienne.org http://www.medieval.org

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Mondo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mondo-devel
Reply | Threaded
Open this post in threaded view
|

Re: [Mondo-devel] Mondo Archive v3.2.2-r3578: ASSERTION FAILED: `call[0]!='\0''

spezialist
Hi Bruno,

Tell, please, in what rpm-file from ftp://ftp.mondorescue.org/test/rhel/6/x86_64 this bug is fixed? The freshest file is dated on April 26...

Very thanks for the support.

30.05.2016 04:07, Bruno Cornec <[hidden email]>

>Hello,
>
> spezialist said on Thu, May 19, 2016 at 12:20:09PM +0300:
> >I found here such error on CentOS-6.7 when using an option -n (mondoarchive tries to mount automatically a NFS resource from /etc/fstab):
>
> Yep, agreed :-(
>
> >==================================================
> >Network share 10.3.33.100:/export/DCIM_backups is not mounted. Trying to mount i
> >ASSERTION FAILED: `call[0]!='\0''
> >        at libmondo-fork.c:53 in call_program_and_get_last_line_of_output
>
> There was an error indeed in a variable used. I should have fixed it in a first beta for 3.2.2 under ftp://ftp.mondorescue.org/test/rhel/6/x86_64
> Let me know if that improves stuff for you.
>
> >Besides, it is possible to see one more bug: in spite of the fact that in command line the tmpdir and scratchdir is /data/tmp/mondo is specified, mondoarchive uses the standard directory /tmp (see a log file).
>
> This is not a bug, but a feature.
> At the start, before any command line parameter analysis, mondoarchive needs to create temp files. So for that it uses the TMPDIR variable (or other look at man page) or /tmp in case none is declared. Later on, it will use the one you precise.
>
> Bruno.
> --
> Open Source Profession, WW Linux Community Lead  http://www.hpintelco.net
> HPE EMEA EG Open Source Technology Strategist http://hp.com/go/opensource
> FLOSS projects:     http://mondorescue.org     http://project-builder.org
> Musique ancienne? http://www.musique-ancienne.org http://www.medieval.org
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
> _______________________________________________
> Mondo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/mondo-devel

--
Чорнобиль форева!

-- реклама -----------------------------------------------------------
Нужна квартира? Нет сразу денег? Банк не даёт кредит? Вариант есть!
Рассрочка на готовое жильё! http://www.milayakvartira.kiev.ua/

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Mondo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mondo-devel