Results 1 to 2 of 2

Thread: A network service error has occurred. [While Sending]

Hybrid View

  1. #1
    Join Date
    Jan 2013
    Posts
    24
    Rep Power
    2

    Default A network service error has occurred. [While Sending]

    Hey Folks,

    I have been running on this installation of Zimbra for several months now with no trouble. This morning, one of our techs managed to loop one of our switches, and brought most of the network down. I am not sure if the mail issue is related, but now whenever we try to send mail, it gives us this error:

    A network service error has occurred.

    Details: [added *s in place of some information.]

    method: [unknown]
    msg: system failure: MessagingExecption
    code: service.FAILURE
    detail: soap:Receiver
    trace: qtp1415079679-102:https://10.0.0.*:443/service/soap/Se...892264c370c994
    request:

    Body: {
    SendMsgRequest: {
    _jsns: "urn:zimbraMail",
    m: {
    e: [
    // [0]:
    {
    a: "******@gmail.com",
    t: "t"
    },
    // [1]:
    {
    a: "user@******.k12.**.us",
    p: "Users name",
    t: "f"
    }
    ],
    idnt: "85cbf54f-70eb-48b6-89a1-f8d8ba4661d0",
    mp: [
    // [0]:
    {
    ct: "multipart/alternative",
    mp: [
    // [0]:
    {
    content: {
    _content: "test

    Weston

    "
    },
    ct: "text/plain"
    },
    // [1]:
    {
    content: {
    _content: "<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div>test<br></div><div><br></div><div><span name="x"></span>Weston<span name="x"></span><br></div><div><br></div></div></body></html>"
    },
    ct: "text/html"
    }
    ]
    }
    ],
    su: {
    _content: "test"
    }
    },
    suid: 1359650467149
    }
    },
    Header: {
    context: {
    _jsns: "urn:zimbra",
    account: {
    _content: "user@******.k12.**.us",
    by: "name"
    },
    authToken: "(removed)",
    session: {
    _content: 1204,
    id: 1204
    },
    userAgent: {
    name: "ZimbraWebClient - FF18 (Win)",
    version: "8.0.1_GA_5438"
    }
    }
    }


    Here are the contents of my zimbra.log file:



    Jan 31 10:28:57 mail amavis[2896]: Using primary internal av scanner code for ClamAV-clamd
    Jan 31 10:28:57 mail amavis[2896]: initializing Mail::SpamAssassin (0)
    Jan 31 10:28:57 mail zimbramon[1009]: 1009:info: Starting antivirus via zmcontrol
    Jan 31 10:28:57 mail amavis[2896]: SA info: config: SpamAssassin failed to parse line, "blogger.co.id" is not valid for "util_rb_2tld", skipping: util_rb_2tld blogger.co.id
    Jan 31 10:28:57 mail amavis[2896]: SA info: config: SpamAssassin failed to parse line, "blogger.co.il" is not valid for "util_rb_2tld", skipping: util_rb_2tld blogger.co.il
    Jan 31 10:28:57 mail amavis[2896]: SA info: config: SpamAssassin failed to parse line, "blogger.com.au" is not valid for "util_rb_2tld", skipping: util_rb_2tld blogger.com.au
    Jan 31 10:28:57 mail amavis[2896]: SA info: config: SpamAssassin failed to parse line, "blogger.com.co" is not valid for "util_rb_2tld", skipping: util_rb_2tld blogger.com.co
    Jan 31 10:28:57 mail amavis[2896]: SA info: config: SpamAssassin failed to parse line, "blogger.com.my" is not valid for "util_rb_2tld", skipping: util_rb_2tld blogger.com.my
    Jan 31 10:28:57 mail amavis[2896]: SA info: config: SpamAssassin failed to parse line, "blogger.com.pe" is not valid for "util_rb_2tld", skipping: util_rb_2tld blogger.com.pe
    Jan 31 10:28:57 mail amavis[2896]: SA info: config: SpamAssassin failed to parse line, "blogger.com.ph" is not valid for "util_rb_2tld", skipping: util_rb_2tld blogger.com.ph
    Jan 31 10:28:57 mail amavis[2896]: SA info: config: SpamAssassin failed to parse line, "blogspot.co.nz" is not valid for "util_rb_2tld", skipping: util_rb_2tld blogspot.co.nz
    Jan 31 10:28:57 mail amavis[2896]: SA info: config: SpamAssassin failed to parse line, "blogspot.co.uk" is not valid for "util_rb_2tld", skipping: util_rb_2tld blogspot.co.uk
    Jan 31 10:28:57 mail amavis[2896]: SA info: config: SpamAssassin failed to parse line, "blogspot.com.ar" is not valid for "util_rb_2tld", skipping: util_rb_2tld blogspot.com.ar
    Jan 31 10:28:57 mail amavis[2896]: SA info: config: SpamAssassin failed to parse line, "blogspot.com.au" is not valid for "util_rb_2tld", skipping: util_rb_2tld blogspot.com.au
    Jan 31 10:28:57 mail amavis[2896]: SA info: config: SpamAssassin failed to parse line, "blogspot.com.br" is not valid for "util_rb_2tld", skipping: util_rb_2tld blogspot.com.br
    Jan 31 10:28:57 mail amavis[2896]: SA info: config: SpamAssassin failed to parse line, "blogspot.com.es" is not valid for "util_rb_2tld", skipping: util_rb_2tld blogspot.com.es
    Jan 31 10:28:57 mail clamd[2946]: clamd daemon 0.97.5-broken-compiler (OS: linux-gnu, ARCH: x86_64, CPU: x86_64)
    Jan 31 10:28:57 mail clamd[2946]: Log file size limited to 20971520 bytes.
    Jan 31 10:28:57 mail clamd[2946]: Reading databases from /opt/zimbra/data/clamav/db
    Jan 31 10:28:57 mail clamd[2946]: Not loading PUA signatures.
    Jan 31 10:28:57 mail clamd[2946]: Bytecode: Security mode set to "TrustSigned".
    Jan 31 10:28:59 mail amavis[2896]: SA info: rules: meta test T_FM_PAYING_LOWER has dependency 'FB_LOWER_PAYM' with a zero score
    Jan 31 10:28:59 mail amavis[2896]: SpamControl: init_pre_fork on SpamAssassin done
    Jan 31 10:28:59 mail amavis[2896]: extra modules loaded after daemonizing/chrooting: /opt/zimbra/conf/spamassassin/sandbox-hstern.pm, /opt/zimbra/zimbramon/lib/Net/libnet.cfg, Mail/SpamAssassin/Plugin/FreeMail.pm, Mail/SpamAssassin/Plugin/SpamCop.pm, Net/Cmd.pm, Net/Config.pm, Net/SMTP.pm
    Jan 31 10:29:05 mail clamd[2946]: Loaded 1724706 signatures.
    Jan 31 10:29:06 mail clamd[2946]: LOCAL: Unix socket file /opt/zimbra/data/clamav/clamav.sock
    Jan 31 10:29:06 mail clamd[2946]: LOCAL: Setting connection queue length to 200
    Jan 31 10:29:06 mail clamd[3042]: Limits: Global size limit set to 20480000 bytes.
    Jan 31 10:29:06 mail clamd[3042]: Limits: File size limit set to 20480000 bytes.
    Jan 31 10:29:06 mail clamd[3042]: Limits: Recursion level limit set to 16.
    Jan 31 10:29:06 mail clamd[3042]: Limits: Files limit set to 10000.
    Jan 31 10:29:06 mail clamd[3042]: Archive support enabled.
    Jan 31 10:29:06 mail clamd[3042]: Algorithmic detection enabled.
    Jan 31 10:29:06 mail clamd[3042]: Portable Executable support enabled.
    Jan 31 10:29:06 mail clamd[3042]: ELF support enabled.
    Jan 31 10:29:06 mail clamd[3042]: Mail files support enabled.
    Jan 31 10:29:06 mail clamd[3042]: OLE2 support enabled.
    Jan 31 10:29:06 mail clamd[3042]: PDF support enabled.
    Jan 31 10:29:06 mail clamd[3042]: HTML support enabled.
    Jan 31 10:29:06 mail clamd[3042]: Self checking every 600 seconds.
    Jan 31 10:29:07 mail zimbramon[1009]: 1009:info: Starting snmp via zmcontrol
    Jan 31 10:29:07 mail zimbramon[1009]: 1009:info: Starting spell via zmcontrol
    Jan 31 10:29:07 mail zimbramon[1009]: 1009:info: Starting mta via zmcontrol
    Jan 31 10:29:07 mail saslauthd[3251]: detach_tty : master pid is: 3251
    Jan 31 10:29:07 mail saslauthd[3251]: ipc_init : listening on socket: /opt/zimbra/data/sasl2/state/mux
    Jan 31 10:29:08 mail opendkim[3267]: OpenDKIM Filter v2.6.0 starting (args: -x /opt/zimbra/conf/opendkim.conf -u zimbra)
    Jan 31 10:29:10 mail zimbramon[1009]: 1009:info: Starting stats via zmcontrol
    Jan 31 10:29:14 mail sshd[3039]: Accepted password for wgeorge from 10.2.2.95 port 50021 ssh2
    Jan 31 10:29:18 mail zmconfigd[1667]: Fetching All configs
    Jan 31 10:29:18 mail zmconfigd[1667]: All configs fetched in 0.07 seconds
    Jan 31 10:29:18 mail zmconfigd[1667]: Tracking service antispam
    Jan 31 10:29:18 mail zmconfigd[1667]: Watchdog: service antispam now available for watchdog.
    Jan 31 10:29:18 mail zmconfigd[1667]: Tracking service antivirus
    Jan 31 10:29:18 mail zmconfigd[1667]: Watchdog: service antivirus now available for watchdog.
    Jan 31 10:29:18 mail zmconfigd[1667]: Tracking service ldap
    Jan 31 10:29:18 mail zmconfigd[1667]: Watchdog: service ldap now available for watchdog.
    Jan 31 10:29:18 mail zmconfigd[1667]: Tracking service logger
    Jan 31 10:29:18 mail zmconfigd[1667]: Watchdog: service logger now available for watchdog.
    Jan 31 10:29:18 mail zmconfigd[1667]: Tracking service mailbox
    Jan 31 10:29:18 mail zmconfigd[1667]: Watchdog: service mailbox now available for watchdog.
    Jan 31 10:29:18 mail zmconfigd[1667]: Tracking service mailboxd
    Jan 31 10:29:18 mail zmconfigd[1667]: Watchdog: service mailboxd now available for watchdog.
    Jan 31 10:29:19 mail zmconfigd[1667]: Tracking service mta
    Jan 31 10:29:19 mail zmconfigd[1667]: Watchdog: service mta now available for watchdog.
    Jan 31 10:29:19 mail zmconfigd[1667]: Tracking service sasl
    Jan 31 10:29:19 mail zmconfigd[1667]: Watchdog: service sasl now available for watchdog.
    Jan 31 10:29:19 mail zmconfigd[1667]: Tracking service snmp
    Jan 31 10:29:19 mail zmconfigd[1667]: Watchdog: service snmp now available for watchdog.
    Jan 31 10:29:19 mail zmconfigd[1667]: Tracking service spell
    Jan 31 10:29:19 mail zmconfigd[1667]: Watchdog: service spell now available for watchdog.
    Jan 31 10:29:19 mail zmconfigd[1667]: Tracking service stats
    Jan 31 10:29:19 mail zmconfigd[1667]: Watchdog: service stats now available for watchdog.
    Jan 31 10:29:19 mail zmconfigd[1667]: Watchdog: service antivirus status is OK.
    Jan 31 10:29:20 mail zmconfigd[1667]: All rewrite threads completed in 0.00 sec
    Jan 31 10:29:20 mail zmconfigd[1667]: All restarts completed in 0.00 sec
    Jan 31 10:29:30 mail postfix/postqueue[4473]: fatal: Queue report unavailable - mail system is down
    Jan 31 10:30:00 mail postfix/postqueue[5065]: fatal: Queue report unavailable - mail system is down
    Jan 31 10:30:01 mail postfix/postqueue[5102]: fatal: Queue report unavailable - mail system is down
    Jan 31 10:30:01 mail zimbramon[5079]: 5079:info: 2013-01-31 10:30:01, QUEUE: 0 0
    Jan 31 10:30:20 mail zmconfigd[1667]: Fetching All configs
    Jan 31 10:30:20 mail zmconfigd[1667]: All configs fetched in 0.05 seconds
    Jan 31 10:30:21 mail zmconfigd[1667]: Watchdog: service antivirus status is OK.
    Jan 31 10:30:21 mail zmconfigd[1667]: All rewrite threads completed in 0.00 sec
    Jan 31 10:30:21 mail zmconfigd[1667]: All restarts completed in 0.00 sec
    Jan 31 10:30:30 mail postfix/postqueue[5930]: fatal: Queue report unavailable - mail system is down
    Jan 31 10:31:00 mail postfix/postqueue[5946]: fatal: Queue report unavailable - mail system is down
    Jan 31 10:31:21 mail zmconfigd[1667]: Fetching All configs
    Jan 31 10:31:21 mail zmconfigd[1667]: All configs fetched in 0.04 seconds
    Jan 31 10:31:22 mail zmconfigd[1667]: Watchdog: service antivirus status is OK.
    Jan 31 10:31:22 mail zmconfigd[1667]: All rewrite threads completed in 0.00 sec
    Jan 31 10:31:22 mail zmconfigd[1667]: All restarts completed in 0.00 sec
    Jan 31 10:31:30 mail postfix/postqueue[6172]: fatal: Queue report unavailable - mail system is down
    Jan 31 10:32:00 mail postfix/postqueue[6188]: fatal: Queue report unavailable - mail system is down
    Jan 31 10:32:22 mail zmconfigd[1667]: Fetching All configs
    Jan 31 10:32:22 mail zmconfigd[1667]: All configs fetched in 0.05 seconds
    Jan 31 10:32:23 mail zmconfigd[1667]: Watchdog: service antivirus status is OK.
    Jan 31 10:32:23 mail zmconfigd[1667]: All rewrite threads completed in 0.00 sec
    Jan 31 10:32:23 mail zmconfigd[1667]: All restarts completed in 0.00 sec
    Jan 31 10:32:30 mail postfix/postqueue[6853]: fatal: Queue report unavailable - mail system is down
    Jan 31 10:33:00 mail postfix/postqueue[6870]: fatal: Queue report unavailable - mail system is down
    Jan 31 10:33:23 mail zmconfigd[1667]: Fetching All configs
    Jan 31 10:33:24 mail zmconfigd[1667]: All configs fetched in 0.05 seconds
    Jan 31 10:33:25 mail zmconfigd[1667]: Watchdog: service antivirus status is OK.
    Jan 31 10:33:25 mail zmconfigd[1667]: All rewrite threads completed in 0.00 sec
    Jan 31 10:33:25 mail zmconfigd[1667]: All restarts completed in 0.00 sec
    Jan 31 10:33:30 mail postfix/postqueue[7089]: fatal: Queue report unavailable - mail system is down


    All of our certs should be valid. I just installed them during the fall, and they should be good for 3 years.

    If you need any more info, let me know what, and where to find it. Any help would be greatly appreciated!

  2. #2
    Join Date
    Jan 2013
    Posts
    24
    Rep Power
    2

    Default

    I am not sure what happened, but I was able to start postfix manually, then do a zmcontrol stop/start, and everything seems to be working again. Weird.

Similar Threads

  1. A network service error has occurred.
    By dragon1964 in forum Error Reports
    Replies: 4
    Last Post: 04-04-2010, 12:14 AM
  2. A network service error has occurred.
    By hjmalves in forum Administrators
    Replies: 2
    Last Post: 01-29-2010, 03:24 AM
  3. A network service error has occurred
    By samesisa in forum Administrators
    Replies: 1
    Last Post: 10-09-2009, 04:43 AM
  4. A network service error has occurred
    By samesisa in forum Migration
    Replies: 0
    Last Post: 10-08-2009, 04:46 AM
  5. A network service error has occurred.
    By rlustemberg in forum Administrators
    Replies: 1
    Last Post: 11-29-2006, 03:34 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •