Messages

1

Kloxo-MR Bugs and Requests / Logout button does not work in Feather skin (ok in Simplicity)

« on: 2014-06-05, 16:34:14 »

subject says it all. Button appears in Feather skin to logout, but clicking on it does nothing!
Tried multiple browsers (Firefox/Chrome/Internet Explorer) but none work.
Switching skin to Simplicity makes Logout button change to Logout link and that *does* work OK.
I prefer Feather skin. Please fix.

This problem is exists on version Kloxo-MR 6.5.1.b-2014060401

2

Kloxo-MR Releases / Re: [UPDATE] Fix CentAlt repo in mratwork.repo

« on: 2014-05-29, 23:48:53 »

very weird - problem has gone away on it's own! yum update worked today without any error. I cannot explain it!

3

Kloxo-MR Technical Helps / Re: Monitoring Malicious Activity

« on: 2014-05-29, 00:11:40 »

I highly recommend installing CSF, I recently followed chrisf's instructions here:-

http://forum.mratwork.com/kloxo-mr-tips-and-tricks/installing-csf-alongside-kloxomr-(how-to)/

I can also recommend Chris's sendmail script to keep track/stop spam coming from your server:

http://forum.mratwork.com/kloxo-mr-tips-and-tricks/sendmail-userid-usage-limits-(script-v1-1b)/

Both generate good log files and CSF can alert you to suspicious server activity via email

4

Kloxo-MR Releases / Re: [UPDATE] Fix CentAlt repo in mratwork.repo

« on: 2014-05-28, 15:56:27 »

Mustafa,

I got this to work on two of my three servers. On my main production server (still running 2014041203) it did not work, instead I got this error:


http://qtp.qmailtoaster.com/repos/nodist/repodata/repomd.xml: [Errno 12] Timeout on http://qtp.qmailtoaster.com/repos/nodist/repodata/repomd.xml: (28, 'connect() timed out!')
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: qtp-nodist. Please verify its path and try again


What can fix it?

5

Kloxo-MR Technical Helps / Re: sorry, no mailbox here by that name (chkuser) -- FIXED!

« on: 2014-04-19, 18:59:28 »

Fixed with various combinations of yum reinstall *-toaster, upcp, cleanall and multiple reboots.
I think I read that sometimes upcp needs to be run twice? Did I read that right? Unsure why that would be though...

6

Kloxo-MR Technical Helps / Re: sorry, no mailbox here by that name (chkuser)

« on: 2014-04-19, 18:09:31 »

I see what you are saying, but do not agree. Config changes/repairs or upgrades to one service should not require complete removal of an entire domain or client. Yes, I do have some server technical expertise - I would very much like to have my email working but without the hassle of taking my entire domain down over Easter weekend.

I admit to not being a CentOS superuser, but I know enough to maintain a stable server and know where my limits are.

Kloxo-MR is a great system, and if the little project I have running could justify the cost of course I would be on cpanel. The project is tiny, but while I try and build it up to something I need to keep costs low (aka free LOL!). Kloxo-MR fits the bill in helping me keep my costs low and I thank MR for that!!! :-)

Anyway, as I am away from home over Easter, I was hoping for a quick fix, rather than a domain rebuild - which I really need to do from home.

It's worth noting that the email misconfigure has come about because of a Kloxo-MR upgrade I did just before I came away for Easter, and my point is that an upgrade should not do this.

7

Kloxo-MR Technical Helps / Re: sorry, no mailbox here by that name (chkuser)

« on: 2014-04-19, 16:03:32 »

This is exactly what I was talking about on this thread:

http://forum.mratwork.com/kloxo-mr-technical-helps/fatal-error-when-upgrading/

This is not something that I can do a lot. It means significant down-time for the server. Surely there must be another way?

As an addendum to above, I run 2 domains on one server (a .com and a .co.uk). The .comworks fine (all emails work as they should). The .co.uk I tried adding a new mailbox and that also could not receive emails with the same error. However, they can send. Weird huh?

Any fix without re-installing the whole client?

8

Kloxo-MR Technical Helps / Re: Fatal error when upgrading

« on: 2014-04-19, 15:28:48 »

Sounds great. If that would've worked for me, I would have been very happy. I tried all that but no good. Re-install from scratch was the only solution that worked. Thanks anyway, still a good panel even with it's current problems.

9

Kloxo-MR Technical Helps / sorry, no mailbox here by that name (chkuser) -- FIXED!

« on: 2014-04-19, 15:26:11 »

I have two mailboxes set up on the same kloxo-mr server (currently 6.5.1.b-2014041203). Both mailboxes have worked since this server was on 6.5.0 and have continued to work throughout several 6.5.1.b upgrades. Now, one of them is no longer working, but the other still is.

When I send to the non-working one I get:

Sorry, we were unable to deliver your message to the following address.

<mail@mydomainname.co.uk>:
Remote host said: 550 5.1.1 sorry, no mailbox here by that name (chkuser) [RCPT_TO]

--- Below this line is a copy of the message.

I have tried various reboot, cleanall, restart-mail, restart-all, manual stop/start of qmail, reboot again
all to no avail.

What to fix?

10

Kloxo-MR Technical Helps / Re: Fatal error when upgrading

« on: 2014-04-18, 15:22:48 »

All above suggestions did not work. Only solution was to wipe Kloxo-MR and re-install from scratch and then restore backup. This is not an ideal upgrade solution. A bug-free upgrade path would be great and limit downtime.

11

Kloxo-MR Technical Helps / Re: Fatal error when upgrading

« on: 2014-04-16, 22:14:36 »

command: yum replace mysql --replace-with=mysql55

gives error message:

Error: Package 'mysql' is not installed.

command: yum update php52s

gives error message:

No package php52s available.

12

Kloxo-MR Bugs and Requests / Re: Add SSH authorized key fails (6.5.1.b-2014031701)

« on: 2014-04-13, 16:15:47 »

This bug still exists in Kloxo-MR 6.5.1.b-2014041203

13

Kloxo-MR Releases / Re: [UPDATE] Kloxo 6.5.1.b to 2014040405

« on: 2014-04-13, 14:03:25 »

404 Not Found error

14

Kloxo-MR Technical Helps / Re: Fatal error when upgrading

« on: 2014-04-13, 13:43:26 »

Also, restart-all now gives:


Starting Djbdns for:
  - axfrdns    [FAILED]
  - tinydns    [FAILED]

maybe why? this worked before upgrade

15

Kloxo-MR Technical Helps / Re: Fatal error when upgrading

« on: 2014-04-13, 13:42:30 »

No joy. Still same error message after running that which is

'Fatal error: Class 'mysqli' not found in /usr/local/lxlabs/kloxo/httpdocs/lib/php/sqlitelib.php on line 59'