Sponsored Content
Operating Systems Solaris Sendmai l: libssl.so.0.9.7: open failed Post 302841961 by picolin on Thursday 8th of August 2013 09:35:45 AM
Old 08-08-2013
Sendmai l: libssl.so.0.9.7: open failed

Hey for some reason I think I deleted a critical file for sendmail. I was looking the log file on /var/log/cron for cron, and the file isn't there and I found out the reason why is because I'm missing libssl.so.0.9.7. Im running Solaris 11.
I checked smtp and got the following:

Code:
#svcs -xv /network/smtp
     svc:/network/smtp:sendmail (sendmail SMTP mail transfer agent)
      State: maintenance since August  8, 2013 09:10:06 AM EDT
     Reason: Restarting too quickly.
     See: man -M /usr/share/man -s 1M sendmail
    See: /var/svc/log/network-smtp:sendmail.log
    Impact: This service is not running

I think I'd have to re install it/ I'm afraid this will cause more problems with log files that are needed. If anyone can guide me in how to reinstall this or restore that library I will really appreciate it. I really need the cron log files

thank you in advance

Last edited by Scott; 08-08-2013 at 10:42 AM.. Reason: Please use code tags
 

10 More Discussions You Might Find Interesting

1. Solaris

UnsatisfiedLinkError libLicense.so: ld.so.1: java: fatal: libssl.so.0.9.8: open faile

Hi Guys, Please help me out. I am new to solaris. I am using solaris 10 ___________________________________________________________ public class Filecheck{ public static void main(String args) { System.out.println("LD_LIBRARY_PATH is : "+System.getProperty("java.library.path"));... (5 Replies)
Discussion started by: josh_chrisin
5 Replies

2. Shell Programming and Scripting

Failed to open output file Error

Hi guys, I Have written a script,In that it will call another file which contains the sql quaries. while wxecuting that I am getting the below exception 01/16|06:28:06:16800: Operating System Error|Failed to open output file Can anybody help me about this,,Its urgent (0 Replies)
Discussion started by: Anji
0 Replies

3. Solaris

libCstd.so.1: open failed

Morning all, I have a problem with a Sun workstation which is running Solaris 8. When I attempt to open an application, the executable fails with this message : "fatal: libcstd.so.1: open failed: No such file or directory" It was suggested to me that I need to add these patches to fix the... (4 Replies)
Discussion started by: AndyD
4 Replies

4. Solaris

Error:: libm.so.2:open failed

Hi, I am working with solaris 9 and I want to install perforce on that,so I downloaded the p4v.bin file and try to install it by the command ./p4v after that it is giving the error--- ld.so.1: ./p4v.bin: fatal: libm.so.2: open failed: No such file or directory Killed I am not... (3 Replies)
Discussion started by: smartgupta
3 Replies

5. Solaris

Solaris10..Open boot diagnostic failed

Hi all, when am rebooting the server (SF v890) we are facing "open boot diagnostic failed". Thanks in Adv. (5 Replies)
Discussion started by: arjunreddy3
5 Replies

6. Solaris

libucb.s0.1: open failed...

Hi all. I try to start an application, but libucb.so1 is missing. # appl23 # appl23ld.so.1: appl23: fatal: libucb.so1: open failed: No such file or directory killed # # ldd appl23 libXm.so.3 => /usr/lib/libXm.so.3 libMrm.so.3 => /usr/lib/libMrm.so.3 ... (14 Replies)
Discussion started by: wolfgang
14 Replies

7. UNIX for Dummies Questions & Answers

NDM: Source file open failed. Error= 2

Hi, I have try to ndm to one server to another server. but i am getting this error. what is this error? are files not in source folder? Source file open failed. Error= 2 Regards, Balamurgan (1 Reply)
Discussion started by: krbala1985
1 Replies

8. Red Hat

rpmdb open failed

Hi, # yum --skip-broken -y update rpmdb: Thread/process 6657/3078387392 failed: Thread died in Berkeley DB library error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages index using db3 - (-30974) error: cannot open... (3 Replies)
Discussion started by: sef alislam
3 Replies

9. UNIX for Beginners Questions & Answers

Rdesktop - ERROR: Failed to open keymap en-us

I just updated my rdesktop to 1.8.3 from source ( on Slackware 11 ) and had troubles with arrow keys/page up/page down not working. I see this on the console: ERROR: Failed to open keymap en-us The fix is a permission change. I initially looked at /usr/share/rdesktop/keymaps and everything... (1 Reply)
Discussion started by: agentrnge
1 Replies

10. Shell Programming and Scripting

Linux open failed: No such file or directory error

Hi, The below commands works fine on serverB . /etc/profile; cd /export/home/user2/utils/plugin/ ./runme.shHowever, when i run the same commands from serverA it fails $ ssh -q user2@serverB ". /etc/profile; cd /export/home/user2/utils/plugin; ./runme.sh"Output Error: Please find the below... (8 Replies)
Discussion started by: mohtashims
8 Replies
sendmail(4)							   File Formats 						       sendmail(4)

NAME
sendmail, sendmail.cf, submit.cf - sendmail configuration files SYNOPSIS
/etc/mail/sendmail.cf /etc/mail/submit.cf DESCRIPTION
The sendmail.cf and submit.cf files are the configuration files for sendmail(1M). Starting with version 8.12 of sendmail, which was shipped with version 9 of the Solaris operating system, two configuration files are used for submission and transmission of mail, instead of only sendmail.cf, as before. These are: sendmail.cf Remains the principal sendmail configuration file. Used for the Mail Transmission Agent (MTA). submit.cf Used for the Mail Submission Program (MSP). The MSP is used to submit mail messages. Unlike the MTA, it does not run as an SMTP daemon. The MSP does not require root privileges, thus the two-file model provides better security than the pre-sendmail 8.12 model, in which the MSP ran as a daemon and required root privileges. In the default sendmail configuration, sendmail uses submit.cf, as indicated in ps(1) output. In ps output, you will observe two sendmail invocations, such as the ones below: /usr/lib/sendmail -Ac -q15m /usr/lib/sendmail -bd -q15m The first indicates the use of submit.cf, with the client queue (/var/spool/clientmqueue) being checked--and, if needed, flushed--every 15 minutes. The second invocation runs sendmail as a daemon, waiting for incoming SMTP connections. As shipped, sendmail.cf and, in particular, submit.cf, are appropriate for most environments. Where a knowledgeable system administrator needs to make a change, he should use the following procedures. For sendmail.cf: 1. Change directories to the directory that contains the source files for the configuration files. # cd /etc/mail/cf/cf 2. Create a copy of the sendmail file for your system. # cp sendmail.mc `hostname`.mc 3. Edit `hostname`.mc. Make changes suitable for your system and environment. 4. Run make to generate the configuration file. # /usr/bin/make `hostname`.cf 5. Copy the newly generated file to its correct location. # cp `hostname`.cf /etc/mail/sendmail.cf 6. Restart the sendmail service. # svcadm restart sendmail You must restart sendmail for sendmail.cf file changes to take effect, as indicated in step 6. Steps 4 - 6 can be automated. See Automated Rebuilding of Configuration Files below. For submit.cf: 1. Change directories to the directory that contains the source files for the configuration files. # cd /etc/mail/cf/cf 2. Create a copy of the submit file for your system. # cp submit.mc submit-`hostname`.mc 3. Edit submit-`hostname`.mc. Make changes suitable for your system and environment. 4. Run make to generate the configuration file. # /usr/bin/make submit-`hostname`.cf 5. Copy the newly generated file to its correct location. # cp submit-`hostname`.cf /etc/mail/submit.cf You do not need to restart sendmail for changes to submit.cf to take effect. Steps 4 and 5 can be automated. See Automated Rebuilding of Configuration Files below. Enabling Access to Remote Clients The sendmail(1M) man page describes how the config/local_only property can be set to true or false to disallow or allow, respectively, access to remote clients for unmodified systems. Setting values for the following properties for the service instance svc:/network/smtp:sendmail results in automated (re)building of con- figuration files: path_to_sendmail_mc path_to_submit_mc The values for these properties should be strings which represent the path name of the .mc files referred to in steps 2 and 3 of both pro- cedures above. Recommended values are: /etc/mail/cf/cf/`hostname`.mc /etc/mail/cf/cf/submit-`hostname`.mc Each property, if set, results in the corresponding .mc file being used to (re)build the matching .cf file when the service is started. These properties persist across upgrades and patches. To prevent a patch or upgrade from clobbering your .cf file, or renaming it to .cf.old, you can set the desired properties instead. FILES
/etc/mail/cf/README Describes sendmail configuration files. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsndmr | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ SEE ALSO
make(1S), ps(1), sendmail(1M), svcadm(1M), attributes(5) System Administration Guide: Network Services SunOS 5.11 8 May 2008 sendmail(4)
All times are GMT -4. The time now is 02:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy