Pandora FMS community forums
upgrading the agent to 7.45 - sed error - Printable Version

+- Pandora FMS community forums (http://pandorafms.org/forum)
+-- Forum: Pandora FMS (http://pandorafms.org/forum/forum-3.html)
+--- Forum: Community support (English) (http://pandorafms.org/forum/forum-7.html)
+--- Thread: upgrading the agent to 7.45 - sed error (/thread-15199.html)



upgrading the agent to 7.45 - sed error - [email protected] - 05-19-2020

I'm trying to upgrade to pandorafms_agent_unix-7.0NG.745-200504.x86_64 on oracle linux 6.x and centos 7.x (latest builds).  When I run the update or try to do a fresh install I get an error:

Resolving Dependencies
--> Running transaction check
---> Package pandorafms_agent_unix.x86_64 0:7.0NG.745-200504 will be installed
--> Processing Dependency: /usr/bin/grep for package: pandorafms_agent_unix-7.0NG.745-200504.x86_64
--> Processing Dependency: /usr/bin/sed for package: pandorafms_agent_unix-7.0NG.745-200504.x86_64
--> Processing Dependency: /usr/bin/grep for package: pandorafms_agent_unix-7.0NG.745-200504.x86_64
--> Processing Dependency: /usr/bin/sed for package: pandorafms_agent_unix-7.0NG.745-200504.x86_64
--> Finished Dependency Resolution
Error: Package: pandorafms_agent_unix-7.0NG.745-200504.x86_64 
           Requires: /usr/bin/sed
Error: Package: pandorafms_agent_unix-7.0NG.745-200504.x86_64
           Requires: /usr/bin/grep

I checked the spec for the rpm and as indicated in the dependencies above, it's looking for grep and sed in /usr/bin.  These files are installed in /bin.  I've tried copying those binaries into /usr/bin as well as soft linking but neither seems to satisfy the requirement.  Is there a reason the build references /usr/bin instead of /bin?  

Thanks,
-Rich


RE: upgrading the agent to 7.45 - sed error - aeleus - 05-30-2020

I get a similar error:
.....

---> Package pandorafms_agent_unix.x86_64 0:7.0NG.745-200504 will be an update
--> Processing Dependency: /usr/bin/sed for package: pandorafms_agent_unix-7.0NG.745-200504.x86_64
---> Package python-tdb.x86_64 0:1.3.18-1.el7 will be installed
--> Processing Dependency: /usr/bin/sed for package: pandorafms_agent_unix-7.0NG.745-200504.x86_64
--> Finished Dependency Resolution
--> Running transaction check
---> Package kernel.x86_64 0:3.10.0-957.5.1.el7 will be erased
---> Package pandorafms_agent_unix.x86_64 0:7.0NG.745-200504 will be an update
--> Processing Dependency: /usr/bin/sed for package: pandorafms_agent_unix-7.0NG.745-200504.x86_64
--> Processing Dependency: /usr/bin/sed for package: pandorafms_agent_unix-7.0NG.745-200504.x86_64
--> Processing Dependency: /usr/bin/sed for package: pandorafms_agent_unix-7.0NG.745-200504.x86_64
--> Finished Dependency Resolution
Error: Package: pandorafms_agent_unix-7.0NG.745-200504.x86_64 (Artica)
           Requires: /usr/bin/sed
           Removing: sed-4.2.2-5.el7.x86_64 (@anaconda)
               Not found
           Updated By: sed-4.2.2-6.el7.x86_64 (base)
               Not found
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest


RE: upgrading the agent to 7.45 - sed error - Diego.M - 06-01-2020

Hello

Sorry for the delay, try to install the agent through the .tar.gz file, it should work fine.

https://sourceforge.net/projects/pandora/files/Pandora%20FMS%207.0NG/745/Tarball/

Greetings
Diego


RE: upgrading the agent to 7.45 - sed error - aeleus - 06-01-2020

(06-01-2020, 02:39 PM)Diego.M Wrote: Hello

Sorry for the delay, try to install the agent through the .tar.gz file, it should work fine.

https://sourceforge.net/projects/pandora/files/Pandora%20FMS%207.0NG/745/Tarball/

Greetings
Diego

Thanks for the reply, Diego.

What worked for me was to update sed first ("yum update sed"). I then ran "yum update" and there were no more sed errors.


RE: upgrading the agent to 7.45 - sed error - [email protected] - 06-05-2020

thanks Diego, I'll give that a shot. Will this be fixed in the repositories for .46?


RE: upgrading the agent to 7.45 - sed error - Diego.M - 06-09-2020

Hello,

Investigating the problem we have detected that we had some agents in the repository that were not in the correct format, we have it noted in our list of priorities and I hope that for the 747 version it is solved, since the 746 has already been released.

Greetings
Diego