Re: Amanda 2.6.1 on Solaris 10/Sparc build
What is the ouptput of: ldd /usr/perl5/site_perl/5.8.4/auto/Amanda/Config/libConfig.so Did it list the libamanda you installed? What's the output of: nm /path/to/libamanda-*.so | grep debug_sendsize Jean-Louis Brian Cuttler wrote: I built amanda 2.6.1 on solaris 10 with the following configure command $ ./configure LDFLAGS='-L/usr/sfw/lib -L/opt/sfw/lib -L/usr/local/lib/amanda -R/usr/sfw/lib -R/opt/sfw/lib -R/usr/local/lib/amanda' --with-user=amanda --with-group=sys --with-udpportrange=932,948 --with-tcpportrange=10084,10100 --with-gnutar=/usr/local/bin/tar And environmental variables PATH /usr/local/bin:/usr/sfw/bin:/opt/sfw/bin:/usr/local/bin:/usr/bin:/usr/sbin:/usr/ccs/bin:/usr/bin:/usr/sbin:/usr/ccs/bin:/usr/sbin:/usr/bin LD_LIBRARY_PATH /usr/local/lib:/usr/sfw/lib:/opt/sfw/lib:/usr/lib:/usr/ucblib:/opt/SUNWspro/lib:/usr/ccs/lib:/usr/5lib however we had runtime problems, apparently failing to load /usr/perl5/site_perl/5.8.4/auto/Amanda/Config/libConfig.so < OPTIONS features=9ffe7f; ERROR Script 'amzfs-snapshot' command 'PRE-DLE-AMCHECK': Can't load '/usr/perl5/ site_perl/5.8.4/auto/Amanda/Config/libConfig.so' for module Amanda::Config: ld.s o.1: perl: fatal: relocation error: file /usr/perl5/site_perl/5.8.4/auto/Amanda/ Config/libConfig.so: symbol debug_sendsize: referenced symbol not found at /usr/ perl5/5.8.4/lib/sun4-solaris-64int/DynaLoader.pm line 230. ERROR Script 'amzfs-snapshot' command 'PRE-DLE-AMCHECK': at /usr/perl5/site_per l/5.8.4/Amanda/Config.pm line 11 ERROR Script 'amzfs-snapshot' command 'PRE-DLE-AMCHECK': Compilation failed in r equire at /usr/perl5/site_perl/5.8.4/Amanda/Script_App.pm line 30. ERROR Script 'amzfs-snapshot' command 'PRE-DLE-AMCHECK': BEGIN failed--compilati on aborted at /usr/perl5/site_perl/5.8.4/Amanda/Script_App.pm line 30. ERROR Script 'amzfs-snapshot' command 'PRE-DLE-AMCHECK': Compilation failed in r equire at (eval 2) line 3. ERROR Script 'amzfs-snapshot' command 'PRE-DLE-AMCHECK':...propagated at /usr/perl5/5.8.4/lib/base.pm line 85. ERROR Script 'amzfs-snapshot' command 'PRE-DLE-AMCHECK': BEGIN failed--compilati on aborted at /usr/perl5/site_perl/5.8.4/Amanda/Script.pm line 21. ERROR Script 'amzfs-snapshot' command 'PRE-DLE-AMCHECK': Compilation failed in r equire at (eval 1) line 3. ERROR Script 'amzfs-snapshot' command 'PRE-DLE-AMCHECK':...propagated at /usr/perl5/5.8.4/lib/base.pm line 85. ERROR Script 'amzfs-snapshot' command 'PRE-DLE-AMCHECK': BEGIN failed--compilati on aborted at /usr/local/libexec/amanda/application/amzfs-snapshot line 32. ERROR Script 'amzfs-snapshot' command 'PRE-DLE-AMCHECK' exited with status 255: see /tmp/amanda/client/griffy/selfcheck.20090130093949.debug OK /usr/local/bin/tar executable OK griffyp ERROR [/climsgl: No such file or directory] ERROR Script 'amzfs-snapshot' command 'POST-DLE-AMCHECK': Can't load '/usr/perl5 /site_perl/5.8.4/auto/Amanda/Config/libConfig.so' for module Amanda::Config: ld. so.1: perl: fatal: relocation error: file /usr/perl5/site_perl/5.8.4/auto/Amanda/Config/libConfig.so: symbol debug_sendsize: referenced symbol not found at /usr /perl5/5.8.4/lib/sun4-solaris-64int/DynaLoader.pm line 230. (you get the idea). I thought we needed more perl in the configure, so I added the --with-perlextlibs with the path to the libConfig.so module. $ ./configure LDFLAGS='-L/usr/sfw/lib -L/opt/sfw/lib -L/usr/local/lib/amanda -R/usr/sfw/lib -R/opt/sfw/lib -R/usr/local/lib/amanda' --with-user=amanda --with-group=sys --with-udpportrange=932,948 --with-tcpportrange=10084,10100 --with-gnutar=/usr/local/bin/tar --with-perlextlibs=/usr/perl5/site_perl/5.8.4/auto/Amanda/Config/libConfig.so er - not the answer, so I tried this. $ ./configure LDFLAGS='-L/usr/sfw/lib -L/opt/sfw/lib -L/usr/local/lib/amanda -L/usr/perl5/site_perl/5.8.4/auto/Amanda/Config -R/usr/sfw/lib -R/opt/sfw/lib -R/usr/local/lib/amanda -R/usr/perl5/site_perl/5.8.4/auto/Amanda/Config' --with-user=amanda --with-group=sys --with-udpportrange=932,948 --with-tcpportrange=10084,10100 --with-gnutar=/usr/local/bin/tar also not the answer with the current amcheck output showing these errors. The files seem to be there, I'm just failing to load them and I'm don't know the proper syntax to do so. Any help with the build apreciated. thank you, Brian Amanda Backup Client Hosts Check ERROR: griffy: Script 'amzfs-snapshot' command 'PRE-DLE-AMCHECK': Can't load '/usr/perl5/site_perl/5.8.4/auto/Amanda/Config/libConfig.so' for module Amanda::Config: ld.so.1: perl: fatal: relocation error: file /usr/perl5/site_perl/5.8.4/auto/Amanda/Config/libConfig.so: symbol debug_sendsize: referenced symbol not found at /usr/perl5/5.8.4/lib/sun4-solaris-64int/DynaLoader.pm line 230. ERROR: gri
Re: Amanda 2.6.1 on Solaris 10/Sparc build
On Sat, Jan 31, 2009 at 9:25 AM, Gunnarsson, Gunnar wrote: > I got the same problem >> ldd usr/perl5/site_perl/5.8.4/auto/Amanda/Config/libConfig.so | grep amanda >libamglue.so => /opt/sfw/lib/amanda/libamglue.so >libamanda-2.5.2p1.so => /opt/sfw/lib/libamanda-2.5.2p1.so > I had older version installed on the system and build with > LDFLAGS=-L/opt/sfw/lib -R/opt/sfw/lib which has > worked for eralier version such as 2.6.1b2-20090108 etc. Obviously, inter-linking different Amanda versions like this is going to be problematic. This sort of thing happens sometimes on my development systems, where I'm running the latest release of Amanda (in /usr/), but of course developing the bleeding edge. The key thing to note is that Amanda is "selecting" a library version at install time; you'll note in the above ldd output that ldd is searching not just for libamanda, but for libamanda-2.5.2p1. I'm sure there are several ways to solve this, but the one that comes to mind is simply removing the old amanda libraries from /opt/sfw/lib before running 'make install' to install the new libraries. Dustin -- Storage Software Engineer http://www.zmanda.com
Re: Amanda 2.6.1 on Solaris 10/Sparc build
Thank you all for your help. output of ldd is > ldd /usr/perl5/site_perl/5.8.4/auto/Amanda/Config/libConfig.so libamglue.so => /usr/local/lib/amanda/libamglue.so libamanda-2.4.5.so =>/opt/sfw/lib/libamanda-2.4.5.so libm.so.2 => /usr/lib/libm.so.2 libgmodule-2.0.so.0 => /usr/local/lib/libgmodule-2.0.so.0 libgobject-2.0.so.0 => /usr/local/lib/libgobject-2.0.so.0 libgthread-2.0.so.0 => /usr/local/lib/libgthread-2.0.so.0 libpthread.so.1 => /usr/lib/libpthread.so.1 libthread.so.1 =>/usr/lib/libthread.so.1 librt.so.1 =>/usr/lib/librt.so.1 libglib-2.0.so.0 => /usr/local/lib/libglib-2.0.so.0 libiconv.so.2 => /usr/local/lib/libiconv.so.2 libresolv.so.2 =>/usr/lib/libresolv.so.2 libintl.so.8 => /usr/local/lib/libintl.so.8 libcrypto.so.0.9.7 =>/usr/sfw/lib/libcrypto.so.0.9.7 libnsl.so.1 => /usr/lib/libnsl.so.1 libsocket.so.1 =>/usr/lib/libsocket.so.1 libc.so.1 => /usr/lib/libc.so.1 libgen.so.1 => /lib/libgen.so.1 libcurses.so.1 =>/lib/libcurses.so.1 libintl.so.1 => /lib/libintl.so.1 libgcc_s.so.1 => /usr/sfw/lib/libgcc_s.so.1 libgcc_s.so.1 => /usr/local/lib/libgcc_s.so.1 libaio.so.1 => /lib/libaio.so.1 libmd.so.1 =>/lib/libmd.so.1 libsec.so.1 => /usr/lib/libsec.so.1 libmp.so.2 =>/lib/libmp.so.2 libscf.so.1 => /lib/libscf.so.1 libavl.so.1 => /lib/libavl.so.1 libdoor.so.1 => /lib/libdoor.so.1 libuutil.so.1 => /lib/libuutil.so.1 libcrypto_extra.so.0.9.7 => /usr/sfw/lib/libcrypto_extra.so.0.9.7 /platform/SUNW,Sun-Fire-V240/lib/libc_psr.so.1 /platform/SUNW,Sun-Fire-V240/lib/libmd_psr.so.1 it all resolves but I do see that libamanda is v2.4.5 and that can't be good. I did a # make uninstall, I'd thought before the build, but I ran it a number of times across a number of builds... do I need to run the make uninstall from my 2.4.5 installation directory ? Is it a matter of changing the order my libraries are specified in, or can I skip /opt/sfw/bin entirely ? Output of the # nm command was not (to me) enlightening, and is probably an artifact of linking the wrong library. > /usr/xpg4/bin/nm -A /opt/sfw/lib/libamanda-2.4.5.so /opt/sfw/lib/libamanda-2.4.5.so: thank you, Brian On Sat, Jan 31, 2009 at 11:08:36AM -0500, Dustin J. Mitchell wrote: > On Sat, Jan 31, 2009 at 9:25 AM, Gunnarsson, Gunnar > wrote: > > I got the same problem > >> ldd usr/perl5/site_perl/5.8.4/auto/Amanda/Config/libConfig.so | grep amanda > >libamglue.so => /opt/sfw/lib/amanda/libamglue.so > >libamanda-2.5.2p1.so => /opt/sfw/lib/libamanda-2.5.2p1.so > > I had older version installed on the system and build with > > LDFLAGS=-L/opt/sfw/lib -R/opt/sfw/lib which has > > worked for eralier version such as 2.6.1b2-20090108 etc. > > Obviously, inter-linking different Amanda versions like this is going > to be problematic. > > This sort of thing happens sometimes on my development systems, where > I'm running the latest release of Amanda (in /usr/), but of course > developing the bleeding edge. > > The key thing to note is that Amanda is "selecting" a library version > at install time; you'll note in the above ldd output that ldd is > searching not just for libamanda, but for libamanda-2.5.2p1. > > I'm sure there are several ways to solve this, but the one that comes > to mind is simply removing the old amanda libraries from /opt/sfw/lib > before running 'make install' to install the new libraries. > > Dustin > > -- > Storage Software Engineer > http://www.zmanda.com --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.
Re: Amanda 2.6.1 on Solaris 10/Sparc build
On Mon, Feb 2, 2009 at 9:39 AM, Brian Cuttler wrote: > I did a # make uninstall, I'd thought before the build, but I > ran it a number of times across a number of builds... do I need > to run the make uninstall from my 2.4.5 installation directory ? That would be one solution. The problem is that the linker is seeing /opt/sfw/lib/libamanda.so -> libamanda-2.4.5.so at install time, and recording the soname libamanda-2.4.5.so at that time. So as long as the libam*2.4.5 libraries aren't in the linker's search path at install time, you should get your libraries linked correctly. Dustin -- Storage Software Engineer http://www.zmanda.com
Re: Amanda 2.6.1 on Solaris 10/Sparc build
man amzfs-snapshot You must give to the 'amanda' user the right to execute some zfs command. Use 'zfs allow' or set the 'PFEXEC' and 'PFEXEC-PATH' properties. Brian Cuttler wrote: Yes! leaving the /opt/sfw/lib out of the path entirely seems to have done the trick, we linked against the correct library and I can now proceed with the next level of errors. Could have sworn I saw something about this on the list last week and I am checking the wiki now. ERROR: griffy: cannot create snapshot 'griffyp/clim...@amanda-_griffyp_climsgl-check': permission denied
Re: Amanda 2.6.1 on Solaris 10/Sparc build
Dustin, On Mon, Feb 02, 2009 at 10:16:38AM -0500, Dustin J. Mitchell wrote: > On Mon, Feb 2, 2009 at 9:39 AM, Brian Cuttler wrote: > > I did a # make uninstall, I'd thought before the build, but I > > ran it a number of times across a number of builds... do I need > > to run the make uninstall from my 2.4.5 installation directory ? > > That would be one solution. The problem is that the linker is seeing > /opt/sfw/lib/libamanda.so -> libamanda-2.4.5.so > at install time, and recording the soname libamanda-2.4.5.so at that > time. So as long as the libam*2.4.5 libraries aren't in the linker's > search path at install time, you should get your libraries linked > correctly. Yes! leaving the /opt/sfw/lib out of the path entirely seems to have done the trick, we linked against the correct library and I can now proceed with the next level of errors. Could have sworn I saw something about this on the list last week and I am checking the wiki now. ERROR: griffy: cannot create snapshot 'griffyp/clim...@amanda-_griffyp_climsgl-check': permission denied ERROR: griffy: unknown response: ERROR: griffy: Script 'amzfs-snapshot' command 'PRE-DLE-AMCHECK' exited with status 1: see /tmp/amanda/client/griffy/selfcheck.20090202110932.debug ERROR: griffy: cannot open 'griffyp/clim...@amanda-_griffyp_climsgl-check': dataset does not exist ERROR: griffy: unknown response: ERROR: griffy: Script 'amzfs-snapshot' command 'POST-DLE-AMCHECK' exited with status 1: see /tmp/amanda/client/griffy/selfcheck.20090202110932.debug Extracted from the debug file. 233590973.228779: selfcheck: Spawning "/usr/local/libexec/amanda/application/am zfs-snapshot amzfs-snapshot POST-DLE-AMCHECK --execute-where client --config gri ffy --host griffy --disk /griffyp/climsgl --device /griffyp/climsgl --df-path /u sr/sbin/df --pfexec YES --pfexec-path /usr/bin/pfexec --zfs-path /usr/sbin/zfs" in pipeline 1233590973.938316: selfcheck: script: ERROR cannot open 'griffyp/clim...@amanda- _griffyp_climsgl-check': dataset does not exist 1233590973.938404: selfcheck: script: 1233590973.947884: selfcheck: checking disk /griffyp/hiu 1 thank you, Brian > Dustin > > -- > Storage Software Engineer > http://www.zmanda.com --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.
Re: Amanda 2.6.1 on Solaris 10/Sparc build
Jean-Louis, On Mon, Feb 02, 2009 at 12:08:13PM -0500, Jean-Louis Martineau wrote: > man amzfs-snapshot > > You must give to the 'amanda' user the right to execute some zfs command. > Use 'zfs allow' or set the 'PFEXEC' and 'PFEXEC-PATH' properties. I found that I had errors in my definitions of PFEXEC-PATH and PFEXEC, both in which modules I'd written them in and in my cutting and pasting/ partial editing, ie pfexec-path is NOT /usr/sbin/zfs That helped but I still had permission errors, I can delve into those if it will be of general help to developers or the list, but I did ultimately use # zfs allow, which resolved the remaining errors and has allowed me to produce snapshots ! I have successfully dumped one zfs partitons with snapshots so far, I will test a little more extensively and then try a restore, then I will be looking to push this server into production to replace a machine which is largely a samba server at an alternate work site. ZFS allowing me to better control samba usage by shares, moving from several large/overcrowded spindles to a ZFS Raid2 config. Once this is done, we recompile for x86 architecture and bring the new (Sun/Solaris) x4500 server online as a new/replacement Amanda server and samba server, replacing an SunFire 280R, which with a 100 MBit interface is NOT performing as needed for backups. Not an Amanda issue, we just out-grew our capacity. thank you, Brian > Brian Cuttler wrote: > >Yes! leaving the /opt/sfw/lib out of the path entirely seems to have > >done the trick, we linked against the correct library and I can now > >proceed with the next level of errors. > > > >Could have sworn I saw something about this on the list last week > >and I am checking the wiki now. > > > >ERROR: griffy: cannot create snapshot > >'griffyp/clim...@amanda-_griffyp_climsgl-check': permission denied > > > --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.
