Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - Giblet535

Pages: [1]
I ran through the 7 upgrade docs. Checked what it suggests. I don't see any problems.

I'm watching zentyal.log, and nothing gets logged when the system stops routing WAN traffic.

If I click a "Change" button for an interface, the orange Save button lights up. Clicking that gets things working again for another 10 minutes. It takes about five minutes.

Syslog gets a LOT of entries.

Is there something I should look for, explicitly?

I upgraded from 6.1 to 6.2 about a month ago. My system updates manually.

Have there really been no updates to Ubuntu - none at all - in a whole month? That's not how Ubuntu works. That's not how any of this works.

I'm thinkin' my apt sources are busted... I get no errors from 'apt update', but that "All packages are up to date." message at the end is creepy and dystopian.

Is there an easy way to put them back to stock?

Edit: Or, is possible that Zentyal is ignoring my setting for Automatic Updates?

I mean, my sources.list looks OK.
Code: [Select]
Hit:1 6.2 InRelease
Hit:2 jessie InRelease
Hit:3 6.1 InRelease
Hit:4 bionic InRelease
Hit:5 bionic-updates InRelease
Hit:6 trusty InRelease
Hit:7 bionic-backports InRelease
Hit:8 public InRelease
Hit:9 bionic InRelease
Hit:10 bionic-security InRelease
Hit:11 xenial InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.

Installation and Upgrades / [SOLVED] Upgrade from 5.1 - dpkg fails
« on: December 06, 2019, 02:11:26 pm »
I upgraded from 5.1, which upgrades Ubuntu to 18.04LTS.

dpkg fails with:
Code: [Select]
fetchmail: no mailservers have been specified.

This causes all of the Zentyal mail packages to fail to configure. The upgrade is stuck at around 98% completion...

I don't use any fetches from other mail servers, and probably never will, so of course no mailservers are configured!

How can I get around this?

Zentyal 4.2...

If an outsider requests mail relay and the message's "From:" includes one of Zentyal's configured virtual domains, then postfix will relay that email, no authentication at all.

I have fairly restrictive rules set in /etc/postfix/
reject_non_fqdn_recipient, reject_non_fqdn_sender, reject_unlisted_recipient, reject_unauth_pipelining, permit_sasl_authenticated, reject_unauth_destination, reject_invalid_hostname, reject_invalid_helo_hostname, reject_unknown_sender_domain, reject_unknown_recipient_domain, check_helo_access pcre:/etc/postfix/helo_checks.pcre

Not even local host should be able to relay w/o authenticating and yet I can see mail being relayed in /var/log/mail.log! One way to relay, a dozen ways to fail... Yet it's like an open relay!

I see no authentication messages in mail.log, and I suspect that Zentyal's authentication mechanism through LDAP is broken somehow.

Please. Someone help me troubleshoot this before anyone else gets spammed.

Installation and Upgrades / Can't send email - Postfix is not happy
« on: August 10, 2015, 03:56:39 pm »
4.1 install has worked fine for about a year through several upgrades.

This morning, I can't send email. I can receive email in webmail/Outlook/Win10email, but can't send.

/var/log/mail records this error:
timestamp server postfix/sendmail[NNNNNNN]: fatal: usage: sendmail [options]

It looks to me like translating to postfix, Zentyal/OpenChange is using the wrong options to postfix/sendmail.

Installation and Upgrades / [SOLVED] 1000's of Ebox messages to root
« on: January 26, 2015, 06:14:35 pm »
The root user is receiving emails from ebox@localhost at a rate of 8-20 per second.

They all contain the same message:
ebox : problem with defaults entries ; TTY=unknown ; PWD=/ ;

There appear to be bug reports about this, it looks like the devs don't believe the reports, and I have found no corrective action.

How do I stop this? I prefer to fix it vs hiding it, but there's not much information pointing at a cause.

An older release of Zentyal had created a /etc/fetchmailrc file to fetch email from a remote server.

I know that I deleted this entry in the old (3.4, I think) Zentyal release, and that it no longer appeared in the UI. It was that orphaned entry that was causing the ebox errors.

I deleted the entry and restarted fetchmail. Problem solved.

Up until today, and new with Zentyal 4, the mail subsystem had to be restarted before email could be sent (TBird, webmail, Android).

Until today, Mail always displayed in the dashboard as "Running" whether it worked or not.

Today, it shows as "Stopped". The "Start" button displays that starting Mail was successful, but the status still displays "Stopped".

Yet I can send and receive email (for now).

Can someone explain why there are three mail subsystem categories in the web admin user interface? (OpenChange, Mail, and Mail Filter?) Did that really make sense to someone?

How do I troubleshoot "Mail" problems?

I had added an external email account (Google) to fetch email from.
Removing that account allows the Mail subsystem to display as "Running" and it still works.

This appears to be an identical bug to the one in the 3.5 release.

This still doesn't explain why there are three Mail subsystems in the user interface, but then I have not seen the UI team's automobiles: they might have separate Left-Turn, and Right-Turn steering wheels plus a Turn-Stick labeled with arrows pointing up and down. So, not enough data.

Installation and Upgrades / How do I diagnose MAIL STOPPED
« on: August 15, 2014, 01:43:33 pm »
The Mail component has status Stopped. Restart generates a Samba crash report.

Samba is the usual star at any Glitch Party, so where do I start looking for the cause?

Everything else seems to work great. `hostname` resolves to

I'm Linux literate. I can fix a glitchy device driver, but I can't start this mail component.

Ubuntu 14.04.1, Zentyal 3.5 (upgraded - it worked until yesterday afternoon)

Installation and Upgrades / Mail module stopped
« on: June 24, 2014, 09:10:13 pm »
On the web-admin Dashboard, the Mail module is shown as "Stopped".

I click the Restart button and eventually get a green status at the top that says the module was successfully restarted. The module still shows "Stopped", but now there's a "Start" button where it was previously "Restart".

Mail has worked before - long enough to configure Outlook to it, and a couple of ActiveSync devices. Then Outlook went "Disconnected".

How do I begin troubleshooting this? /var/log/zentyal/zentyal.log has 4 of the following entries after attempting to start the mail module. Line 43 of zentyal.psgi appears to be a macro call.

Code: [Select]
WARN> zentyal.psgi:43 main::__ANON__ - Use of uninitialized value $dir_path in concatenation (.) or string at /usr/share/perl5/HTML/Mason/ line 117
Restarting "File Sharing..." allows Outlook to connect again.
Researching this indicates that the DCE RPC plugin for Samba is the cause. DCE...  :-\ Who uses that ancient crap? Oh yeah, THEM. Microsloth....

The samba restart produces a crash report which I submitted, although I doubt Zentyal can do much, other than forward it to OpenChange folks.

Anyway, the Mail module still shows up as "Stopped", even though it apparently isn't.

Pages: [1]