Hi, Please find attached backupexec-ralus-10.1.5629.3.ebuild, backupexec-ralus.rc and backupexec-ralus.confd. backupexec-ralus is the Symantec Backup Exec Remote Agent for Lunix and Unix Servers (RALUS). RALUS "enables Windows Server network administrators to perform backup and restore operations on Linux, Unix and Solaris hosts that are connected to the network." Symantec Backup Exec "is the industry leading Windows data protection solution designed for disk, providing continuous, comprehensive, cost-effective, high-performance, and certified backup and recovery." BT
Created attachment 74907 [details] backupexec-ralus-10.1.5629.3 ebuild
Created attachment 74908 [details] backupexec-ralus-10.1.5629.21 conf.d
Created attachment 74909 [details] backupexec-ralus-10.1.5629.21 init.d
Quick change of platform in bugzilla. Sorry about the email.
(In reply to comment #1) > Created an attachment (id=74907) [edit] > the backupexec-ralus ebuild > The enewgroup beoper needs to be run from pkg_preinst() or pkg_setup(), or the group won't be added when installing from binary packages... See bug 124680.
Created attachment 83853 [details] backupexec-ralus-10.1.5629.3 ebuild
Comment on attachment 83853 [details] backupexec-ralus-10.1.5629.3 ebuild moved enewgroup beoper from src_install() to pkg_preinst().
(In reply to comment #7) > (From update of attachment 83853 [details] [edit]) > moved enewgroup beoper from src_install() to pkg_preinst(). > You are fast! I tried to get this running on a box today, was not very successful. While messing with the ebuild I noticed a couple of other problems... The chmod -R 600 ${WORKDIR}/etc will probably wreak all sorts of havoc on a system (having /etc rw-------). Ditto with the perms on /opt and /var...
Thanks for the feedback. I've been waiting a while now for someone to check it out and find problems. Regarding the permissions, I wasn't too sure of what kind of permissions to set, so I just used the permissions from the manual installation of the remote agent. Check page 814 to 816 of the Backup Exec Administrator
Thanks for the feedback. I've been waiting a while now for someone to check it out and find problems. Regarding the permissions, I wasn't too sure of what kind of permissions to set, so I just used the permissions from the manual installation of the remote agent. Check page 814 to 816 of the Backup Exec Administrators Guide. http://seer.support.veritas.com/docs/279401.htm I'm currently working on a new ebuild which applies a security hot fix and brings it to version 10.1.5629.21. It should be ready in a day or two. I'm also trying to avoid the renaming of the fetched file. After I updated the ebuild for the enewgroup issue, I come across this error message when merging. Looks pretty bad, but I don't know what it means or how to fix it. The agent stills works as usual. scanelf: rpath_security_checks(): Security problem with relative DT_RPATH '.' in /var/tmp/portage/backupexec-ralus-10.1.5629.3/image//opt/VRTSralus/bin/beremote scanelf: rpath_security_checks(): Security problem with relative DT_RPATH '.' in /var/tmp/portage/backupexec-ralus-10.1.5629.3/image//opt/VRTSralus/bin/libbe_util.so scanelf: rpath_security_checks(): Security problem with relative DT_RPATH '.' in /var/tmp/portage/backupexec-ralus-10.1.5629.3/image//opt/VRTSralus/bin/libbebsdu.so scanelf: rpath_security_checks(): Security problem with relative DT_RPATH '.' in /var/tmp/portage/backupexec-ralus-10.1.5629.3/image//opt/VRTSralus/bin/libbedscomn.so scanelf: rpath_security_checks(): Security problem with relative DT_RPATH '.' in /var/tmp/portage/backupexec-ralus-10.1.5629.3/image//opt/VRTSralus/bin/libbedssmsp.so scanelf: rpath_security_checks(): Security problem with relative DT_RPATH '.' in /var/tmp/portage/backupexec-ralus-10.1.5629.3/image//opt/VRTSralus/bin/libbedsvx.so scanelf: rpath_security_checks(): Security problem with relative DT_RPATH '.' in /var/tmp/portage/backupexec-ralus-10.1.5629.3/image//opt/VRTSralus/bin/libbeengsvr.so scanelf: rpath_security_checks(): Security problem with relative DT_RPATH '.' in /var/tmp/portage/backupexec-ralus-10.1.5629.3/image//opt/VRTSralus/bin/libbenetapi.so scanelf: rpath_security_checks(): Security problem with relative DT_RPATH '.' in /var/tmp/portage/backupexec-ralus-10.1.5629.3/image//opt/VRTSralus/bin/libbenetns.so scanelf: rpath_security_checks(): Security problem with relative DT_RPATH '.' in /var/tmp/portage/backupexec-ralus-10.1.5629.3/image//opt/VRTSralus/bin/libbenettcp.so scanelf: rpath_security_checks(): Security problem with relative DT_RPATH '.' in /var/tmp/portage/backupexec-ralus-10.1.5629.3/image//opt/VRTSralus/bin/libbenetutl.so scanelf: rpath_security_checks(): Security problem with relative DT_RPATH '.' in /var/tmp/portage/backupexec-ralus-10.1.5629.3/image//opt/VRTSralus/bin/libbestdutl.so scanelf: rpath_security_checks(): Security problem with relative DT_RPATH '.' in /var/tmp/portage/backupexec-ralus-10.1.5629.3/image//opt/VRTSralus/bin/libbetools.so scanelf: rpath_security_checks(): Security problem with relative DT_RPATH '.' in /var/tmp/portage/backupexec-ralus-10.1.5629.3/image//opt/VRTSralus/bin/libeng_dsss.so scanelf: rpath_security_checks(): Security problem with relative DT_RPATH '.' in /var/tmp/portage/backupexec-ralus-10.1.5629.3/image//opt/VRTSralus/bin/libndmp_dsss.so scanelf: rpath_security_checks(): Security problem with relative DT_RPATH '.' in /var/tmp/portage/backupexec-ralus-10.1.5629.3/image//opt/VRTSralus/bin/libndmp_loops.so scanelf: rpath_security_checks(): Security problem with relative DT_RPATH '.' in /var/tmp/portage/backupexec-ralus-10.1.5629.3/image//opt/VRTSralus/bin/libndmp_tpfmt.so scanelf: rpath_security_checks(): Security problem with relative DT_RPATH '.' in /var/tmp/portage/backupexec-ralus-10.1.5629.3/image//opt/VRTSralus/bin/libndmpcomm.so scanelf: rpath_security_checks(): Security problem with relative DT_RPATH '.' in /var/tmp/portage/backupexec-ralus-10.1.5629.3/image//opt/VRTSralus/bin/libsmstools.so scanelf: rpath_security_checks(): Security problem with relative DT_RPATH '.:../lib' in /var/tmp/portage/backupexec-ralus-10.1.5629.3/image//opt/VRTSralus/bin/libvxACE.so scanelf: rpath_security_checks(): Security problem with relative DT_RPATH '../lib' in /var/tmp/portage/backupexec-ralus-10.1.5629.3/image//opt/VRTSralus/bin/libvxACE.so scanelf: rpath_security_checks(): Security problem with relative DT_RPATH '.:../lib' in /var/tmp/portage/backupexec-ralus-10.1.5629.3/image//opt/VRTSralus/bin/libvxicudata.so scanelf: rpath_security_checks(): Security problem with relative DT_RPATH '../lib' in /var/tmp/portage/backupexec-ralus-10.1.5629.3/image//opt/VRTSralus/bin/libvxicudata.so scanelf: rpath_security_checks(): Security problem with relative DT_RPATH '.:../lib' in /var/tmp/portage/backupexec-ralus-10.1.5629.3/image//opt/VRTSralus/bin/libvxicuuc.so scanelf: rpath_security_checks(): Security problem with relative DT_RPATH '../lib' in /var/tmp/portage/backupexec-ralus-10.1.5629.3/image//opt/VRTSralus/bin/libvxicuuc.so
(In reply to comment #9) > I'm currently working on a new ebuild which applies a security hot fix and > brings it to version 10.1.5629.21. It should be ready in a day or two. I'm also > trying to avoid the renaming of the fetched file. I don't know if this is taboo or not, but I changed the unpack to: tar xfz ${DISTDIR}/${RALUS_FILE_SRC} || die I removed the check for the gz file because it was kind of redundant, the unpack fails without it anyhow... As far as all of the scanelf warnings, I believe that has to do with scanelf being sensitive to RPATHS with . (current working directory) in them. It is a warning, not a showstopper, as far as I know ;) When I installed the ebuild, the init script started beremote, but indicated an error during startup. I set up the ralus.cfg, but my workstation never showed up on the console, I attempted to add it as a user defined path and it failed. I have been using the version 8/9 agent for a while, perhaps I just got something wrong in ralus.cfg. Does 10 not use some mechanism like the old agent.cfg to export paths? Regardless, I add root to the beremote group and tried to connect as root, no go. I have also read that you have to install a license on the server for it to even show up, not sure about that. If that is the case, I will stick with the old "free" agent. As far as the perms, I changed them to match what already existing on my box, 755 for /etc and /var, I also applied more restrictive perms to the various directories it created in /var. This might have been the reason it was not working for me ;) I will give your new ebuild a try though...
> Regardless, I add root to the beremote group and tried to connect as root, no Er, I meant to write beoper group, or whatever the correct group is.
Created attachment 83859 [details] backupexec-ralus-10.1.5629.21 ebuild new ebuild. it applies a security hotfix (http://tinyurl.com/otvxo) and brings the version to 10.1.5629.21. I have removed the need to rename the fetched file, by using tar instead of unpack. removed checking of the source files. fixed some permissions problems.
(In reply to comment #10) I have found some info on the scanelf warnings at http://tinyurl.com/l8438. It seems this issue will be fixed in portage 2.1 which is currently unstable. I believe the permission problems are now fixed. Although the previous method never ruined my permissions, it's better to be safe. This ebuild requires rpm as a build dependency. It also uses cpio. Do you know if I need to add cpio as build dependency or is cpio part of the base commands in Gentoo? Regarding the remote agent license. A license is required for your Linux/Unix remote agents if your Backup Exec server is licensed. This only applies from 10 onwards. Previous versions of Linux/Unix remote agents did not require a license. However, you can use Backup Exec 10.1 (10d) and the remote agents for 60 days without a license. This ebuild/agent only works with Backup Exec 10 and higher. I haven't had any experience with versions prior to 10.1, but here is a dump of my ralus.cfg file. Software\VERITAS\Backup Exec\Agent Browser\TcpIp\AdvertisementPort=6101 Software\VERITAS\Backup Exec\Engine\Agents\Advertising Interval Minutes=5 Software\VERITAS\Backup Exec\Engine\Agents\Agent Directory List 1=<media server> Software\VERITAS\Backup Exec\Engine\Logging\RANT NDMP Debug Level=0 Software\VERITAS\Backup Exec\Engine\RALUS\Encoder= Software\VERITAS\Backup Exec\Engine\RALUS\SystemExclude1=/dev/*.* Software\VERITAS\Backup Exec\Engine\RALUS\SystemExclude2=/proc/*.* Software\VERITAS\Backup Exec\Engine\RALUS\SystemExclude3=/mnt/nss/pools/ Software\VERITAS\Backup Exec\Engine\RALUS\SystemExclude4=/mnt/nss/.pools/
Created attachment 83947 [details] backupexec-ralus-10.1.5629.21 ebuild Updated backupexec-ralus-10.1.5629.21 ebuild. Merging of the hotfix files has been moved from src_install() to src_unpack(). Added a line to delete the init script that is provided by the orginal package. Fixed the permissions that are set on the package files.
Created attachment 83953 [details] backupexec-ralus-10.1.5629.21 ebuild Another update. Minor change to remove rpm build dependency.
Created attachment 83961 [details] backupexec-ralus-10.1.5629.21 init.d Minor update. Converted some spaces to tabs.
Created attachment 83962 [details] backupexec-ralus-10.1.5629.21 ebuild Minor update. Converted some spaces to tabs.
Backup bugs for evaluation by app-backup team.
Is there a more specific product page for this package aside from www.veristas.com?
(In reply to comment #19) > Is there a more specific product page for this package aside from > www.veristas.com? > I don't believe there is a product page for the remote agent. It is not a separate product and is part of Backup Exec, although it is provided as a separate download. The only specific pages that I have found are the knowledge base articles for the remote agent and the remote agent hotfix. http://seer.support.veritas.com/docs/279329.htm http://seer.support.veritas.com/docs/282308.htm The Backup Exec Administrator's Guide contains specific information about installing the remote agent on page 803. http://seer.support.veritas.com/docs/279401.htm You can also take a look at the Backup Exec site to find product information about Back Exec. http://www.backupexec.com/ Here is the knowledge base article for the Backup Exec installation files for Windows. http://seer.support.veritas.com/docs/279332.htm To find these knowledge base articles, you can go to http://www.veritas.com/ and under "VERITAS Resources" click on "VERITAS Product Support". Then select "Backup Exec Server Products" in the "Product List" and select "Backup Exec for Windows Servers" under "Select Product". In the "Ask a question" field type "RALUS" to bring up all knowledgebase articles about the remote agent.
This binary package has to many security/qa problems to allow it in the tree. Please work with upstream to fix the textrels and bad rpaths and release a new version. Vs ../lib it should be using $ORIGIN ; shared objects must always be compiled with -fPIC
(In reply to comment #21) > This binary package has to many security/qa problems to allow it in the tree. > Please work with upstream to fix the textrels and bad rpaths > and release a new version. Vs ../lib it should be using $ORIGIN ; > shared objects must always be compiled with -fPIC > Based on this, I'm going to close this as WONTFIX. If the upstream maintainer can fix the issues addressed please resubmit an ebuild for consideration.
Thanks for taking the time to consider this ebuild. I doubt upstream will fix any of the problems with the package since Gentoo is not supported. However, I will try and contact them anyway.
Created attachment 91386 [details] updated init script. This is an updated init script for backupexec-ralus. The one included above did not work for me, as ralus spawns 4 processes, and start-stop-daemon could not stop them with the default signal 15. I hope this helps someone else!
Comment on attachment 91386 [details] updated init script. #!/sbin/runscript checkconfig() { if [ -z "$BEREMOTE_OPTS" ]; then eerror "You must set config options in /etc/conf.d/backupexec-ralus" return 1 fi } start() { local retstatus=1 local maxtry=15 # delete pidfile rm -f /var/VRTSralus/ralus.pid rm -f /var/VRTSralus/ralus.errpid # display to the user what you're doing ebegin "Starting Symantec Backup Exec Remote Agent" #run the checkconfig function checkconfig || return 1 # Start the process as a daemon, records it's own pid... start-stop-daemon --start --quiet --background --name beremote --exec /opt/VRTSralus/bin/beremote -- ${BEREMOTE_OPTS} >/dev/null 2>&1 while [ "$maxtry" != "0" ]; do if [ -f /var/VRTSralus/ralus.pid ]; then maxtry=0 else maxtry=$(($maxtry-1)) sleep 1; fi if [ -f /var/VRTSralus/ralus.errpid ]; then maxtry=0 fi done if [ -f /var/VRTSralus/ralus.pid ]; then retstatus=0 else retstatus=1 fi # output success or failure eend $retstatus } stop() { # display a message to the user ebegin "Stopping Symantec Backup Exec Remote Agent" # stop the daemon using exec path and name. There are multiple pids... start-stop-daemon --stop --quiet --signal 9 --name beremote --exec /opt/VRTSralus/bin/beremote # delete pidfile rm -f /var/VRTSralus/ralus.pid rm -f /var/VRTSralus/ralus.errpid # output success or failure eend $? }
Created attachment 91387 [details] updated init script. Attached incorrect file previously -- sorry.
Work on this ebuild has moved to the Gentoo Linux Wiki. http://gentoo-wiki.com/HOWTO_Symantec_Backup_Exec_Remote_Agent_for_Linux_and_Unix_Servers