Postfix/postdrop warning in logs

On some 10.6.8 client Macs I'm seeing these entries in the system logs.  These are just basic client Macs and shouldn't be doing anything mail related other than basic email via MS Outlook 2011.
10/25/11 9:51:06 AM    com.apple.launchd[1]    (org.postfix.master) Failed to count the number of files in "/var/spool/postfix/maildrop": No such file or directory
10/25/11 9:51:11 AM    postfix/master[89381]    daemon started -- version 2.5.5, configuration /etc/postfix
10/25/11 9:51:11 AM    postfix/pickup[89382]    63DAC308062D: uid=0 from=<root>
10/25/11 9:51:11 AM    postfix/cleanup[89384]    63DAC308062D: message-id=<[email protected]>
10/25/11 9:51:11 AM    postfix/qmgr[89383]    63DAC308062D: from=<[email protected]>, size=6156, nrcpt=1 (queue active)
10/25/11 9:51:11 AM    postfix/local[89386]    63DAC308062D: to=<[email protected]>, orig_to=<root>, relay=local, delay=288469, delays=288469/0.06/0/0.02, dsn=2.0.0, status=sent (delivered to file: /dev/null)
10/25/11 9:51:11 AM    postfix/qmgr[89383]    63DAC308062D: removed
and this in the mail.log file:
Oct 25 09:51:03 udp015338uds postfix/postdrop[34961]: warning: mail_queue_enter: create file maildrop/812308.34961: No such file or directory
Oct 25 09:51:03 udp015338uds postfix/postdrop[71803]: warning: mail_queue_enter: create file maildrop/812413.71803: No such file or directory
Oct 25 09:51:11 udp015338uds postfix/master[89381]: daemon started -- version 2.5.5, configuration /etc/postfix
Oct 25 09:51:11 udp015338uds postfix/pickup[89382]: 63DAC308062D: uid=0 from=<root>
Oct 25 09:51:11 udp015338uds postfix/cleanup[89384]: 63DAC308062D: message-id=<[email protected]>
Oct 25 09:51:11 udp015338uds postfix/qmgr[89383]: 63DAC308062D: from=<[email protected]>, size=6156, nrcpt=1 (queue active)
Oct 25 09:51:11 udp015338uds postfix/local[89386]: 63DAC308062D: to=<[email protected]>, orig_to=<root>, relay=local, delay=288469, delays=288469/0.06/0/0.02, dsn=2.0.0, status=sent (delivered to file: /dev/null)
Oct 25 09:51:11 udp015338uds postfix/qmgr[89383]: 63DAC308062D: removed
What is likely the cause?  How can I fix/stop it?
These Macs have ssh locked down with hosts.allow and sshd_config configured to only only certain subnets and users so I don't think they've compromised via ssh.
Thanks

Update: It turns out those postdrop errors in the log were actually only 3 errors that kept repeating. I ended up killing those three processes since SMTP was working properly and I figured that those must be processes that were stuck and for some reason wouldn't end. After that, no more repeat errors in the log, but I am getting messages about:
Warning: database /etc/aliases.db is older than source file /etc/aliases
I issued sudo postmap aliases, but got the error: postmap: fatal: open aliases: No such file or directory.
Any ideas?

Similar Messages

  • Mail: postfix/pipe : warning: pipe_command_write: write time limit ..

    Anyone run into the following situation:
    1) "postfix/pipe : warning: pipecommandwrite: write time limit exceeded" error messages start showing up in system.log
    2) The postfix queue starts filling up with mail to be delivered for a particular user. User reports that mail is not being delivered.
    3) The user has a hung IMAPd process that refuses to die. kill -9 <pid> does not work for the process, and a hard reset of the server is needed (push the button since shutdown hangs due to the hung imapd process) to get things back in order. Also, a reconstruct of the users mailbox seems to smooth things out after the reboot.
    The postfix/pipe message seems to indicate that postfix is unable to deliver the mail, which is why it's sitting in the queue. I'm guessing that the hung IMAPd process has locked out the users mailbox, or something of that nature.
    Right now, I have a script that tails the system.log, grep's for these messages and sends me an email with the contents of the postfix queue. This helps alert me to the situation, but it would be nice to either fix it or get a better idea of what's going on.
    The user usually affected by this is using Mail.app on 10.4.11.
    Thanks in Advance,
    Flatrack

    YESSSSS!!! I am having this same problem on a server that I'm administering. Talk about incredibly frustrating. I'm seeing the exact same behavior:
    One user's IMAP process gets hung up and gradually takes down the entire service. No amount of Force Quitting or "kill"-ing will work...that process just keeps on staying hung up. And soft restarting is ineffective.
    In my case, it is the same user every time. I had it happen once in January (while I was out of town, of course), then not again until 3-4 times this past Thursday-Saturday (yep, the server knew I was out of town again). End user told me today that he'd had to force quit Mail several times recently...during the same timeframe as the hangups. I have done some major cleaning up, overhauling, and mailbfr-ing of this user's account, and will be watching it like a hawk for some time to come, but the main problem I see is:
    *SO WHAT* if a lone user's account gets corrupted?!?! Or if the end user jerks the rug out from under Mail by Force Quitting?!?! In NO WAY should that cause such a problem that the server won't even soft restart or allow that IMAP process to be killed. This is causing me a large Mac OS X Server credibility headache right now. My tech liaison and I have been gradually transitioning from PC + Exchange Server to Mac + Leopard Server, and having a single user's fouled up email account bring down the whole works is NOT acceptable.
    What can we do to further fix/debug/repair this? Of course the user account can be rebuilt, but this should not be taking the entire IMAP service down and then not allowing the server to restart or kill off the process.
    Fred

  • Sending Email - postdrop: warning: unable to lookup public/pickup...

    I am trying to setup some RAID monitoring tools on an older G4 QuickSilver under 10.3.9. It seems however that I cannot send out any email from the server using /usr/bin/mail. I am getting the error:
    postdrop: warning: unable to look up public/pickup: No such file or directory
    Now I've found some material on the subject that suggests migrating to postfix away from sendmail, but I need the Apple Developer Kit (SDK?) for 10.3.x, of which there doesn't seem to be one. Do I just use the 10.2.x kit or can the 10.4.x or 10.5 developer kits be used?

    This URL helped me with the same issue:
    http://www.manning-sandbox.com/thread.jspa?messageID=51841
    I just dropped JSP and went with facelets.

  • ARC1: Warning.  Log sequence in archive filename wrapped

    Hi
    we are using oracle10g 10.2.0.3 on windows 2000 server
    we are getting ARC1: Warning. Log sequence in archive filename wrapped messages in alerlog
    full messages is ARC1: Warning. Log sequence in archive filename wrapped
    to fix length as indicated by %S in LOG_ARCHIVE_FORMAT.
    Old log archive with same name might be overwritten.
    what could be the reason?
    Thanks
    OH

    user3308982 wrote:
    Hi
    we are using ARC%S_%R.%T
    and we didn't change format
    last few days we are getting this warning message
    Thanks
    With Regards
    OHinstead of %S with %s on LOG_ARCHIVE_FORMAT,Then try again

  • RMAN-08120: WARNING: archived log not deleted, not yet applied by standby

    i get RMAN-08120: WARNING: archived log not deleted, not yet applied by standby on primary
    but when i run below query i get the same result from primary and standby
    SQL> select max(sequence#) from v$archived_log;
    MAX(SEQUENCE#)
    44051
    SQL>
    standby is one log switch behind only!

    i get RMAN-08120: WARNING: archived log not deleted, not yet applied by standby on primary You already have answer by post of Mseberg.
    but when i run below query i get the same result from primary and standby
    SQL> select max(sequence#) from v$archived_log;
    MAX(SEQUENCE#)
    44051
    SQL>
    standby is one log switch behind only!this is wrong query used on primary & standby. even if any one of archive gap available lets suppose sequence *44020* , this archive not transported to standby due to some network problem and so on. later if archives from *44021* all the archives transported on standby upto *44051* , then it shows the maximum sequence transferred to standby, It wont shows applied sequence.
    Check the below queries.
    Primary:-
    SQL> select thread#,max(sequence#) from v$archived_log group by thread#;
    Standby:-
    SQL> select thread#,max(sequence#) from v$archived_log where applied='YES' group by thread#;
    HTH.

  • ARC0: Warning.  Log sequence in archive filename wrapped

    Hi,
    I am having my production database(Oracle 11gR1) in windows 2003 server.
    I am often getting below archive warnings in alert logs.
    ARC0: Warning. Log sequence in archive filename wrapped
    to fix length as indicated by %S in LOG_ARCHIVE_FORMAT.
    Old log archive with same name might be overwritten.
    1.Could any one tell the reason and how to resolve this?
    2.Also i want to know the limitations of %s and %S in LOG_ARCHIVE_FORMAT?
    my log_archive_format is set to string ARC%S_%R.%T

    Vikash Jain (DBA Trainee) wrote:
    Hi,
    I am having my production database(Oracle 11gR1) in windows 2003 server.
    I am often getting below archive warnings in alert logs.
    ARC0: Warning. Log sequence in archive filename wrapped
    to fix length as indicated by %S in LOG_ARCHIVE_FORMAT.
    Old log archive with same name might be overwritten.
    1.Could any one tell the reason and how to resolve this?
    2.Also i want to know the limitations of %s and %S in LOG_ARCHIVE_FORMAT?
    my log_archive_format is set to string ARC%S_%R.%T
    Change log archive format to small(s) *%s* instead of *%S*
    %S Specifies the log sequence number.  This number is padded to the left by
       zeroes.  The default value is one with a range of up to five characters.
    %s Specifies the log sequence number.  The number is not padded.  The default
       value is one with no range limit on characters. also refer this link http://docs.oracle.com/cd/B19306_01/server.102/b14237/initparams103.htm

  • WARNING: archive log not deleted as it is still needed

    Our Oralce Database is a single node database of version 10.1.0.
    Dataguard/Standby is not configured.....we are executing the following command for archivelog backup
    run
    allocate channel c1 device type sbt;
    backup archivelog all delete input;
    This script is successfull in backingup all the archvied log files however it is not deleteing the input files. Instead it gives the warning....
    "WARNING: archive log not deleted as it is still needed"
    What could be the problem?

    If you do a Metalink seach on "WARNING: archive log not deleted as it is still needed." you'll find a couple of documents that explain the issue.
    The short answer is that RMAN has backed up logs which have not yet shipped to standby, so it won't delete them, cause they're still needed till they're successfully shipped to standby.
    -Mark

  • Mail.log postfix/smtp warning

    Hi!
    Since a few days I get thousands of warnings of this kind in mail.log of my server 10.5.8:
    Jun 26 18:22:03 xserver postfix/smtpd[39255]: warning: 91.93.147.18: hostname host-91-93-147-18.teletektelekom.com verification failed: nodename nor servname provided, or not known
    Jun 26 18:22:13 xserver postfix/smtpd[39257]: warning: 187.4.192.19: hostname 187-4-192-19.fnsce704.e.brasiltelecom.net.br verification failed: nodename nor servname provided, or not known
    Jun 26 18:23:01 xserver postfix/smtpd[39255]: warning: 88.247.132.249: hostname dsl88-247-34041.ttnet.net.tr verification failed: nodename nor servname provided, or not known
    Jun 26 18:23:06 xserver postfix/smtpd[39257]: warning: 216.227.244.233: hostname 233.244.227.216.ictxwavemedia.net verification failed: nodename nor servname provided, or not known
    Jun 26 18:24:19 xserver postfix/smtpd[39255]: warning: 85.105.145.11: hostname dsl.static.85-105-37131.ttnet.net.tr verification failed: nodename nor servname provided, or not known
    Jun 26 18:24:42 xserver postfix/smtpd[39257]: warning: 187.58.65.10: hostname 187.58.65.10.static.gvt.net.br verification failed: nodename nor servname provided, or not known
    Jun 26 18:24:53 xserver postfix/smtpd[39020]: warning: 95.111.46.12: hostname ip-95-111-46-12.home.megalan.bg verification failed: nodename nor servname provided, or not known
    Jun 26 18:25:39 xserver postfix/smtpd[39257]: warning: 88.250.166.251: hostname dsl88-250-42747.ttnet.net.tr verification failed: nodename nor servname provided, or not known
    Jun 26 18:26:22 xserver postfix/smtpd[39257]: warning: 212.102.9.115: hostname shabnet9-115.shabakah.net verification failed: nodename nor servname provided, or not known
    Jun 26 18:26:38 xserver postfix/smtpd[39255]: warning: 122.160.122.156: hostname ABTS-North-Static-156.122.160.122.airtelbroadband.in verification failed: nodename nor servname provided, or not known
    Jun 26 18:26:47 xserver postfix/smtpd[39020]: warning: 91.205.155.250: hostname BB-155-250.018.net.il verification failed: nodename nor servname provided, or not known
    Jun 26 18:27:29 xserver postfix/smtpd[39257]: warning: 91.93.147.18: hostname host-91-93-147-18.teletektelekom.com verification failed: nodename nor servname provided, or not known
    I don't know what is the meaning?? SPAM-Attack?
    What can I do to stop it?
    It is also impossible to start ServerAdmins maintenance-tasks...
    Thank you for your assistance,
    Peter.

    Hi again!
    I tried to do a backup of my mailsystem with "mailbfr -b".
    The backup started fine and gave me a lost of messages like this and after almost an hour mailbfr quit with an error message:
    file has vanished: "/private/var/spool/postfix/active/F3C8D1B2F878"
    file has vanished: "/private/var/spool/postfix/active/F3CE11994C58"
    file has vanished: "/private/var/spool/postfix/active/F3CE91CA9F23"
    file has vanished: "/private/var/spool/postfix/active/F3D0219C94B3"
    file has vanished: "/private/var/spool/postfix/active/F3DA11CAE5FA"
    file has vanished: "/private/var/spool/postfix/active/F3DAF1BFE84D"
    file has vanished: "/private/var/spool/postfix/active/F3E101AAEBE0"
    file has vanished: "/private/var/spool/postfix/active/F3E2218FB617"
    file has vanished: "/private/var/spool/postfix/active/F3E3A18D70FF"
    file has vanished: "/private/var/spool/postfix/defer/0/045C01EE7ABE"
    file has vanished: "/private/var/spool/postfix/defer/0/0478E18D9F63"
    file has vanished: "/private/var/spool/postfix/defer/0/04B1F1EC6134"
    file has vanished: "/private/var/spool/postfix/defer/0/04B8D1E905AA"
    file has vanished: "/private/var/spool/postfix/defer/0/04EA31E9AEFD"
    file has vanished: "/private/var/spool/postfix/defer/0/050B11EF1208"
    file has vanished: "/private/var/spool/postfix/defer/0/051071E50E17"
    file has vanished: "/private/var/spool/postfix/defer/0/0513A199DDE7"
    file has vanished: "/private/var/spool/postfix/defer/0/0525E1E9AE61"
    file has vanished: "/private/var/spool/postfix/deferred/A/A0A971E9694B"
    file has vanished: "/private/var/spool/postfix/deferred/A/ACACB1EA9334"
    file has vanished: "/private/var/spool/postfix/flush/xserverhlg_hh_schulede"
    file has vanished: "/private/var/spool/postfix/incoming/D9B1B1F8E251"
    rsync warning: some files vanished before they could be transferred (code 24) at /SourceCache/rsync/rsync-35.2/rsync/main.c(992) (sender=2.6.9)
    speed 9600 baud;
    lflags: echoe echoke echoctl pendin
    iflags: iutf8
    oflags: -oxtabs
    cflags: cs8 -parenb
    mailbfr was aborted. The process was NOT completed successfully.
    Starting Mail Services
    Cyrus IMAP successfully started.
    I still can't access the ServerAdmin maintenance section of mail.
    Until now the mail-service seems to work fine but every few seconds I get messages in the mail.log like posted in my first posting.
    Should I give mailbfr a try to repair the maildatabase?
    Greetings from Germany,
    Peter.

  • Postfix/qmgr warning regarding amavis configurations

    Got these during a heavy spam bombardment:
    Sep 11 03:52:15 flatrack postfix/qmgr[43726]: warning: mail for [127.0.0.1]:10024 is using up 4001 of 4001 active queue entries
    Sep 11 03:52:15 flatrack postfix/qmgr[43726]: warning: you may need to reduce smtp-amavis connect and helo timeouts
    Sep 11 03:52:15 flatrack postfix/qmgr[43726]: warning: so that Postfix quickly skips unavailable hosts
    Sep 11 03:52:15 flatrack postfix/qmgr[43726]: warning: you may need to increase the main.cf minimalbackofftime and maximalbackofftime
    Sep 11 03:52:15 flatrack postfix/qmgr[43726]: warning: so that Postfix wastes less time on undeliverable mail
    Sep 11 03:52:15 flatrack postfix/qmgr[43726]: warning: you may need to increase the master.cf smtp-amavis process limit
    Sep 11 03:52:15 flatrack postfix/qmgr[43726]: warning: please avoid flushing the whole queue when you have
    Sep 11 03:52:15 flatrack postfix/qmgr[43726]: warning: lots of deferred mail, that is bad for performance
    Sep 11 03:52:15 flatrack postfix/qmgr[43726]: warning: to turn off these warnings specify: qmgrclog_warntime = 0
    Sep 11 03:54:27 flatrack imap[7175]: login: flatrack.capps.com [65.197.152.201] spam plaintext user logged in
    Sep 11 03:55:03 flatrack imap[7228]: login: flatrack.capps.com [65.197.152.201] junkmail CRAM-MD5 User logged in
    Sep 11 03:57:15 flatrack postfix/qmgr[43726]: warning: mail for [127.0.0.1]:10024 is using up 4179 of 4179 active queue entries
    Sep 11 03:57:15 flatrack postfix/qmgr[43726]: warning: you may need to reduce smtp-amavis connect and helo timeouts
    Sep 11 03:57:15 flatrack postfix/qmgr[43726]: warning: so that Postfix quickly skips unavailable hosts
    Sep 11 03:57:15 flatrack postfix/qmgr[43726]: warning: you may need to increase the main.cf minimalbackofftime and maximalbackofftime
    Sep 11 03:57:15 flatrack postfix/qmgr[43726]: warning: so that Postfix wastes less time on undeliverable mail
    Sep 11 03:57:15 flatrack postfix/qmgr[43726]: warning: you may need to increase the master.cf smtp-amavis process limit
    Sep 11 03:57:15 flatrack postfix/qmgr[43726]: warning: please avoid flushing the whole queue when you have
    Sep 11 03:57:15 flatrack postfix/qmgr[43726]: warning: lots of deferred mail, that is bad for performance
    Sep 11 03:57:15 flatrack postfix/qmgr[43726]: warning: to turn off these warnings specify: qmgrclog_warntime = 0
    sh-3.2# postconf -n
    bouncequeuelifetime = 6h
    brokensasl_authclients = yes
    command_directory = /usr/sbin
    config_directory = /etc/postfix
    content_filter = smtp-amavis:[127.0.0.1]:10024
    daemon_directory = /usr/libexec/postfix
    debugpeerlevel = 2
    delaywarningtime = 6h
    disablevrfycommand = yes
    enableserveroptions = yes
    html_directory = no
    inet_interfaces = localhost
    localrecipientmaps = proxy:unix:passwd.byname $alias_maps
    luser_relay =
    mail_owner = _postfix
    mailboxsizelimit = 0
    mailbox_transport = cyrus
    mailq_path = /usr/bin/mailq
    manpage_directory = /usr/share/man
    mapsrbldomains =
    masquerade_domains = capps.com
    maximalqueuelifetime = 2d
    messagesizelimit = 104857600
    mydestination = $myhostname,localhost.$mydomain,localhost
    mydomain = capps.com
    mydomain_fallback = localhost
    myhostname = flatrack.capps.com
    mynetworks = 127.0.0.0/8,192.168.10.0/24,65.197.152.0/24
    newaliases_path = /usr/bin/newaliases
    queue_directory = /private/var/spool/postfix
    readme_directory = /usr/share/doc/postfix
    relayhost = reefer.capps.com
    sample_directory = /usr/share/doc/postfix/examples
    sendmail_path = /usr/sbin/sendmail
    setgid_group = _postdrop
    smtpdclientrestrictions = permit_mynetworks, permitsaslauthenticated, rejectrblclient zen.spamhaus.org, permit
    smtpddatarestrictions = permit_mynetworks, rejectunauthpipelining, permit
    smtpdhelorequired = yes
    smtpdhelorestrictions = permitsaslauthenticated, permit_mynetworks, checkheloaccess hash:/etc/postfix/helo_access, rejectnon_fqdnhostname, rejectinvalidhostname, permit
    smtpdpw_server_securityoptions = cram-md5,login,plain
    smtpdrecipientrestrictions = rejectinvalidhostname, rejectnon_fqdnsender, rejectnon_fqdnrecipient, permitsaslauthenticated, permit_mynetworks, rejectunauthdestination, rejectunlistedrecipient, rejectrblclient zen.spamhaus.org, permit
    smtpdsasl_authenable = yes
    smtpdsenderrestrictions = permitsasl_authenticated,permit_mynetworks,reject_non_fqdnsender, permit
    smtpduse_pwserver = yes
    unknownlocal_recipient_rejectcode = 550
    virtualmailboxdomains =
    virtual_transport = virtual
    As these variables are not present in main.cf, they are using the default values:
    maximalbackofftime (default: 4000s)
    The maximal time between attempts to deliver a deferred message.
    This parameter should be set to a value greater than or equal to $minimalbackofftime. See also $queuerundelay.
    Time units: s (seconds), m (minutes), h (hours), d (days), w (weeks). The default time unit is s (seconds).
    minimalbackofftime (default: 300s)
    The minimal time between attempts to deliver a deferred message; prior to Postfix 2.4 the default value was 1000s.
    This parameter also limits the time an unreachable destination is kept in the short-term, in-memory, destination status cache.
    This parameter should be set greater than or equal to $queuerundelay. See also $maximalbackofftime.
    Time units: s (seconds), m (minutes), h (hours), d (days), w (weeks). The default time unit is s (seconds).
    Should I do what the messages suggest, and what might be good values to use for these variables.
    Thanks,
    Flatrack

    Looking at your configuration, it strikes me as odd that postfix and amavisd-new could not keep up with each other. Of course I do not know how bad the spam attack was, but judging from the log snippet (there are sometimes minutes between entries) I doubt it was to heavy.
    It would think that amavisd hung for some reason and caused this. In which case increasing timings will not help, but you should find out why amavisd crashed (check amavis.log). For time being, I wouldn't make any changes. If it should happen again, you can take it from there.
    Another thing to check: From your configuration and DNS MX records, it seems like outgoing AND incoming mail go/come through a relay host. Have a look at that hosts configuration as well. Maybe it was relaying a backed up queue to aggressively.
    HTH,
    Alex

  • ASA 5505 Logging Issue - Warning: Configured logging host interface conflicts with route table entry

    I am getting this warning on my ASA 5505 when I try to set up logging from my off site FW to the central FW, which is a 5510. What I am trying to do is send the FW logs through the VPN Tunnel into the central 5510 to our logging server at 192.168.22.99, but allow all other traffic out the outside interface so customers can hit our web servers down there. Here is an example of my config with fake IP's. I get this error when trying to do "logging inside host 192.168.22.99". If I try to put in "logging Tunnel host 192.168.22.99" I get the "Warning:Security Level is 1" message
    5505
    ethe0/0
    desc To LA ISP (217.34.122.1)
    switchport access vlan2
    ethe0/1
    desc To Redwood City HQ via VPN Tunnel
    switchport access vlan1
    ethe0/2
    desc To Internal Web Server
    switchport access vlan3
    VLAN1
    desc Tunnel to HQ
    ifinterface Tunnel
    security level 1
    217.34.122.3 255.255.255.248
    VLAN3
    desc Internal Web Server
    ifinterface inside
    security level 100
    192.168.0.1 255.255.255.0
    access-list LosAngeles extended permit ip 192.168.0.0 255.255.255.0 192.168.22.0 255.255.255.0
    (No access-group is performed, as I match from the crypto map instead since I have multiple sites going out of HQ - see HQ configs)
    route Tunnel 192.168.22.0 255.255.255.0 65.29.211.198
    crypto map TO-HQ 10 match address LosAngeles
    crypto map TO-HQ set peer ip 65.29.211.198
    5510 at HQ
    access-list LA extended permit ip 192.168.22.0 255.255.255.0 192.168.0.0 255.255.255.0
    (again no access-group, since I have a couple other off sites)
    crypto map TO-LA 20 match address LA
    crypto map TO-LA 20 set peer ip 217.34.122.3

    Hi Jouni,
    I have the following configs in place with fake IPs
    5505
    1 outside interface with security level 0 (vlan1 direct connect to isp 217.33.122.2/30) - goes to ISP
    1 Tunnel interface with security level 1 (vlan 2 direct connect to isp 217.33.122.6/30) - goes to Tunnel to our 5510
    1 inside interface with security level 100 (servers connected to hub, with vlan3 ip of 192.168.0.1)
    access-list LosAngeles extended permit ip 192.168.0.0 255.255.255.0 192.168.22.0 255.255.255.0 - acl to 5510 inside network
    route outside 0.0.0.0 0.0.0.0 217.33.122.1 - route for all traffic (except for 192.168.22.0/24) to take the outside connection
    route Tunnel 192.168.22.0 255.255.255.0 65.29.211.198 - route for 192.168.22.0 destined traffic to take the Tunnel connection
    crypto map  TO-HQ 10 match address LosAngeles
    crypto map TO-HQ 10 set peer ip 65.29.211.198
    tunnel-group 65.29.211.198 type ipsec-l2l
    5510
    1 outside interface with security level 0 (vlan1 direct connect to isp 65.29.211.198) - goes to isp
    1 inside interface with security level 100 (vlan2 connection to corporate servers and SIP 192.168.22.0/24)
    access-list LA extended permit ip 192.168.22.0 255.255.255.0 192.168.0.0 255.255.255.0
    access-list OUTBOUND extended permit icmp host 217.33.122.6 host 192.168.22.99 (allows Nagios monitor to ping the DE interface
    access-group OUTBOUND in interface outside
    nat (inside,outside) static 192.168.22.99 interface destination static 217.33.122.6
    route outside 192.168.0.0 255.255.255.0 217.33.122.6
    crypto map TO-LA 20 match address LA
    crypto map TO-LA 20 set peer ip 217.33.122.6
    tunnel-group 217.33.122.6 type ipsec-l2l
    I am mistaken on the 5510 interfaces. They do not have vlans, and the IP address is directly applied to the interfaces for outside and inside.

  • LC_NUMERIC and LC_TIME bash warning when logging into TTY

    I recently re-installed Arch after bouncing around a few distributions, and ever since I completed the install, I've had the following error when logging in to the TTY (only there, never noticed it anywhere else).  Specifically, the error reads:
    -bash: warning: setlocale: LC_NUMERIC: cannot change locale ()
    -bash: warning: setlocale: LC_NUMERIC: cannot change locale ()
    -bash: warning: setlocale: LC_TIME: cannot change locale ()
    -bash: warning: setlocale: LC_TIME: cannot change locale ()
    Output of locale:
    LANG=en_US.UTF-8
    LC_CTYPE="en_US.UTF-8"
    LC_NUMERIC="en_US.UTF-8"
    LC_TIME="en_US.UTF-8"
    LC_COLLATE="en_US.UTF-8"
    LC_MONETARY="en_US.UTF-8"
    LC_MESSAGES="en_US.UTF-8"
    LC_PAPER="en_US.UTF-8"
    LC_NAME="en_US.UTF-8"
    LC_ADDRESS="en_US.UTF-8"
    LC_TELEPHONE="en_US.UTF-8"
    LC_MEASUREMENT="en_US.UTF-8"
    LC_IDENTIFICATION="en_US.UTF-8"
    LC_ALL=
    locale -a
    C
    en_US.utf8
    POSIX
    en_US.UTF-8 is also uncommented in locale.gen, and it's been generated.  I haven't gotten any locale errors in any application I use, and it only appears before the prompt after logging in to a TTY screen.  I've also not set those variables to anything else in /etc/profile, /etc/bash.bashrc, .profile/.bashrc.  Logging into the root user instead of my user account does not result in the errors.  Also, it seems from the error that the locales are being set to "", and I can't for the life of me figure out where it's coming from.  I've searched the forums for similar problems, and most of these errors included warnings about files and folders not existing, which doesn't happen here, and were resolved by re-generating the locale (I've tried it, no change).  The only one that came close was an old forum thread about guarddog generating a different set of locale's using incorrect locale definitions, which resulted in the same errors.  If anyone has a suggestion as to how to fix this (or a handy trick for finding all files where locales are set), I'm open to them.
    .bashrc:
    # .bashrc (2013, Dec 11)
    [ -z "$PS1" ] && return
    # set a fancy prompt (non-color, unless we know we "want" color)
    case "$TERM" in
    xterm-color) color_prompt=yes;;
    esac
    if [ -n "$force_color_prompt" ]; then
    if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
    # We have color support; assume it's compliant with Ecma-48
    # (ISO/IEC-6429). (Lack of such support is extremely rare, and such
    # a case would tend to support setf rather than setaf.)
    color_prompt=yes
    else
    color_prompt=
    fi
    fi
    if [ "$color_prompt" = yes ]; then
    PS1="\[\e[0;37m\]⮀\[\e[0;32m\]\u\[\e[0;36m\]@\[\e[0;32m\]\h\[\e[0;37m\]:\[\e[0;33m\] \W\[\e[0;37m\]\[\e[0;37m\]\$\[\e[0m\] "
    else
    PS1="\[\e[43m\]\[\e[31m\]\u\[\e[0;33m\]\[\e[46m\]⮀\[\e[34m\]\h\[\e[0;36m\]\[\e[47m\]⮀\[\e[33m\]\W\[\e[0;37m\]⮀\[\e[0m\] "
    fi
    unset color_prompt force_color_prompt
    # Alias definitions.
    # You may want to put all your additions into a separate file like
    # ~/.bash_aliases, instead of adding them here directly.
    # See /usr/share/doc/bash-doc/examples in the bash-doc package.
    #if [ -f ~/.bash_aliases ]; then
    # . ~/.bash_aliases
    #fi
    # enable color support of ls and also add handy aliases
    if [ "$TERM" != "dumb" ] && [ -x /usr/bin/dircolors ]; then
    eval "`dircolors -b`"
    alias ls='ls --color=auto'
    #alias dir='ls --color=auto --format=vertical'
    #alias vdir='ls --color=auto --format=long'
    #alias grep='grep --color=auto'
    #alias fgrep='fgrep --color=auto'
    #alias egrep='egrep --color=auto'
    fi
    ##custom aliases
    alias ls="ls -la --color=always --classify"
    alias lh='\ls -a --classify | grep "\."'
    alias halt="sudo shutdown -P now"
    PATH=$PATH:$HOME/.rvm/bin:$HOME/.gem/ruby/2.0.0/bin # Add RVM to PATH for scripting
    .profile:
    # ~/.profile: executed by the command interpreter for login shells.
    # This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login
    # exists.
    # see /usr/share/doc/bash/examples/startup-files for examples.
    # the files are located in the bash-doc package.
    # the default umask is set in /etc/profile
    #umask 022
    # if running bash
    if [ -n "$BASH_VERSION" ]; then
    # include .bashrc if it exists
    if [ -f "$HOME/.bashrc" ]; then
    . "$HOME/.bashrc"
    fi
    fi
    # set PATH so it includes user's private bin if it exists
    if [ -d "$HOME/bin" ] ; then
    PATH="$HOME/bin:$PATH"
    fi
    PATH="$PATH:/usr/local/sbin"
    PATH="$PATH:/usr/local/bin"

    An update:
    I've tried explicitly exporting both variables with en_US.UTF-8 in my bashrc, which has resulted in no change whatsoever.  Checking the value of these variables from my running system yields an empty return (i.e. the variables aren't set).  Can someone let me know if these variables are set on their system?  If they are, I'll see if I can set them manually and if that resolves the issue.

  • Warning in log after updating SQL server when installing cumulative updates

    Every time I install cumulative updates for Lync 2013, when I run the command to update the SQL database which is
    Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn SQLLYNPROD1.domain.local -Verbose
    I get the two warnings below in the log. The update works OK and I don't have any issues. I get a warning just for this database for the database itself and the log path. Can't find anything on it searching. Any idea where to start looking
    Warning: The
    database rtcxds being updated has data file path at
    \\SQLLYNPROD1.domain.local\E$\SQLData\rtcxds.mdf and supplied data file path is
    \\SQLLYNPROD1.domain.local\E$\CsData\BackendStore\(default)\DbPath\rtcxds.mdf.
    Supplied path will be ignored.
    Warning: The
    database rtcxds being updated has log file path at
    \\SQLLYNPROD1.domain.local\F$\SQLLog\rtcxds.ldf and supplied data file path is
    \\SQLLYNPROD1.domain.local\E$\CsData\BackendStore\(default)\LogPath\rtcxds.ldf.
    Supplied path will be ignored.

    There is only one CsData folder on the Lync server but the install program is complaining about the RTCXDS database which is on our enterprise backend SQL server. The path above is correct.
    \\SQLLYNPROD1.domain.local\E$\SQLData\rtcxds.mdf for data and
    \\SQLLYNPROD1.domain.local\F$\SQLLog\rtcxds.ldf  for logs
    but a bogus path of
    \\SQLLYNPROD1.domain.local\E$\CsData\BackendStore\(default)\DbPath\rtcxds.mdf for data and
    \\SQLLYNPROD1.domain.local\E$\CsData\BackendStore\(default)\LogPath\rtcxds.ldf for logs is being supplied from somewhere to the install program.
    Fortunately, the install program knows enough to ignore the supplied path and take what it is given from SQL. Just trying to figure out where this supplied path is coming from. It could be anywhere. As I said, needle in a haystack.

  • [SOLVED] Postfix: activity not being logged

    I installed and configured postfix/cyrus and then sent myself a couple of test messges.  The messages don't show up anywhere, so I ran
    journalctl -u postfix -f
    to see where the problem was, sent myself another message from another machine and got ... nothing.  The only thing displayed are the Start/Stop service messages.
    Does systemd not log service activity for postfix?  I was planning on installing syslog-ng (or rsyslog) anyway, as I need to have message log persistence across reboots, but I thought that this stuff would at least be logged while it's happening.
    Last edited by pgoetz (2015-01-29 11:58:10)

    Never mind, I'm an idiot.  My ISP was blocking port 25 traffic (even though I explicitly asked them if they blocked port 25 when I set up the account, and they responded no).
    So as to not be a complete waste of a human life, here are some simple debugging steps for someone who happens to stumble upon this post.
    From an external host, try telneting to port 25 before doing anything else. 
    $ telnet pgoetz.com 25
    If this hangs, then postfix is either not listening on port 25 or the traffic is being blocked.  At this point, check to make sure that your ISP isn't blocking port 25 traffic.
    If running a firewall, check your firewall rules:
    $ iptables -L
    You should see something that looks like this:
    ACCEPT tcp -- anywhere anywhere tcp dpt:smtp
      If you don't see this, your firewall is blocking traffic to port 25.  See the iptables documentation for fixing this.
    If the firewall is OK, next check to see if postfix is actually listening on the port:
    ss -nlpt | grep 25
      You should see something that looks like this:
    LISTEN 0 100 *:25 *:*
    users:(("smtpd",pid=20261,fd=6),("master",pid=19480,fd=13))
    If you don't see this, there is a good chance that either postfix is not running or inet_interfaces is not configured properly in /etc/postfix/main.cf.  The default value for inet_interfaces is
    inet_interfaces = all
    .  Unless you absolutely know what you're doing, you should leave this set at the default; i.e. don't set this parameter in /etc/postfix/main.cf at all.  To check if postscript is running,
    systemctl status postfix
    or
    ps auxw | grep postfix
    .  If you don't see a line that looks like this:
    root 19480 0.0 0.0 12432 2136 ? Ss 05:58 0:00 /usr/lib/postfix/master -w
    postfix isn't running.
    Finally,
    journalctl -u postfix -f
    is your friend.  Use it early and often when debugging postfix problems.  It will reveal missing files (e.g.
    Jan 16 07:03:29 ibis postfix/local[20277]: error: open database /etc/postfix/aliases.db: No such file or directory
    and anything else that postfix is unhappy about.
    Happy postfixing!

  • SFP+ Voltage low warning useless logging?

    Hi
    4500X switch is continuously logging following errors from one port. SFP in the port is Cisco original SFP+ 10GBase-LR.
    Should the SFP be replaced or is there a way to get rid of this useless error cluttering the log?
    Thanks
    Feb 25 13:26:30.618 eet: %SFF8472-5-THRESHOLD_VIOLATION: Te1/1/15: Voltage low warning; Operating value: 3.09 V, Threshold value: 3.10 V.
    switch#sh int Te1/1/15 transceiver detail
    ITU Channel not available (Wavelength not available),
    Transceiver is internally calibrated.
    mA: milliamperes, dBm: decibels (milliwatts), NA or N/A: not applicable.
    ++ : high alarm, +  : high warning, -  : low warning, -- : low alarm.
    A2D readouts (if they differ), are reported in parentheses.
    The threshold values are calibrated.
                                  High Alarm  High Warn  Low Warn   Low Alarm
              Temperature         Threshold   Threshold  Threshold  Threshold
    Port       (Celsius)          (Celsius)   (Celsius)  (Celsius)  (Celsius)
    Te1/1/15    23.4                75.0        70.0         0.0       -5.0
                                  High Alarm  High Warn  Low Warn   Low Alarm
               Voltage            Threshold   Threshold  Threshold  Threshold
    Port       (Volts)            (Volts)     (Volts)    (Volts)    (Volts)
    Te1/1/15   3.09                  3.60        3.50        3.10       3.00
               Optical            High Alarm  High Warn  Low Warn   Low Alarm
               Transmit Power     Threshold   Threshold  Threshold  Threshold
    Port       (dBm)              (dBm)       (dBm)      (dBm)      (dBm)
    Te1/1/15    -3.1                 3.4         0.4        -8.2      -12.2
               Optical            High Alarm  High Warn  Low Warn   Low Alarm
               Receive Power      Threshold   Threshold  Threshold  Threshold
    Port       (dBm)              (dBm)       (dBm)      (dBm)      (dBm)
    Te1/1/15    -4.8                 3.4         0.4       -14.4      -18.4

    Hi,
    The answer from TAC:
    Explanation:
    This is expected behaviour unless these ports are connected and do not have db loss. If we have the SFP inserted in fibre ports and do not have optical fibre connected further we receive threshold violation errors.
    Action Plan:
    To avoid threshold violation messages on optical ports that are not connected, you should admin shut the port down.
    You can also remove the SFP inserted on these ports to stop the error message.
    HTH

  • RMAN-08137: WARNING: archived log not deleted as it is still needed

    I am trying to delete archive logs older than 7 days in streams environment.
    1) we dont have a standby database
    2) checkpoint_retention_time = 7
    Please help me with this.
    Regards,
    Mike

    SQL> set serveroutput on
    DECLARE
    hScn number := 0;
    lScn number := 0;
    sScn number;
    ascn number;
    alog varchar2(1000);
    begin
    select min(start_scn), min(applied_scn) into sScn, ascn
    from dba_capture;
    DBMS_OUTPUT.ENABLE(2000);
    for cr in (select distinct(a.ckpt_scn)
    from system.logmnr_restart_ckpt$ a
    where a.ckpt_scn <= ascn and a.valid = 1
    and exists (select * from system.logmnr_log$ l
    where a.ckpt_scn between l.first_change# and l.next_change#)
    order by a.ckpt_scn desc)
    loop
    if (hScn = 0) then
    hScn := cr.ckpt_scn;
    else
    lScn := cr.ckpt_scn;
    exit;
    end if;
    end loop;
    if lScn = 0 then
    lScn := sScn;
    end if;
    dbms_output.put_line('Capture will restart from SCN ' || lScn ||' in the following file:');
    for cr in (select name, first_time
    from DBA_REGISTERED_ARCHIVED_LOG
    where lScn between first_scn and next_scn order by thread#)
    loop
    dbms_output.put_line(cr.name||' ('||cr.first_time||')');
    end loop;
    end;
    After i ran the above script from metalink i got the below output.
    When I have run the above code that is given in metalink to check the minimum archive logs required to restart streams i got the below ouput.
    Capture will restart from SCN 55313283790in the following file:
    +FLASH/ORCL/archivelog/2011_02_22/thread_1_seq_842.346.443519740 (11-MAR-11)*
    +FLASH/ORCL/archivelog/2011_02_22/thread_2_seq_832.189.440690538 (11-MAR-11)*
    Does this mean that I will not be able to delete the archive logs from 11-mar-11 ?
    Regards,
    Mike

Maybe you are looking for

  • Connect to SAP gateway failed Connect_PM  TYPE=B

    Hi experts, I get the following error when i ping through JCO destinations on portals. com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM  TYPE=B MSHOST=imtsapdev01 GROUP=CLUST R3NAME=DMI MSSERV=sapm

  • To generate graphs in sap

    HI all, I want to know the function module which will generate  graphs in 2d and 3d in sap from basic lists. Please help its urgent.

  • Outlook synchronising error message

    What version of Windows is being used? XP What Service Pack is installed? SP2 What version of PC Suite is installed? 6.6.16 What is the connection method, cable, bluetooth or IR? cable A few questions about PC Suite Does PC Suite cope with a corporat

  • Visual admin and start/stop dispatcher

    What is the normal procedure for starting and stopping dispatcher.... Is it normally done at UNIX through ./go script? and what is the normal way to shutdown j2ee engine.... just wonder what the standard practice was... Also where do I find the Visua

  • My iPad won't connect to the apple store, how do I fix this?

    My iPad apps are not connecting to the apple store. So I can't update my apps.  What can I do to fix this?