Testing downloading mail:
root@otrs otrs/bin# ./PostMasterMailbox.pl
ERROR: No such file or directory:
/usr/share/otrs/Kernel/Config/Files/ZZZAuto.pm
ERROR: OTRS-PMAccount-10 Perl: 5.10.1 OS: linux Time: Thu Jun 30 22:29:48
2011
Message: POP3: Can't connect to 192.168.10.10
Traceback (2578):
Module: Kernel::System::MailAccount::POP3::_Fetch (v1.6.2.1) Line: 87
Module: Kernel::System::MailAccount::POP3::Fetch (v1.6.2.1) Line: 45
Module: Kernel::System::MailAccount::MailAccountFetch (v1.9) Line: 380
Module: main::Fetch (v1.10) Line: 181
Module: ./PostMasterMailbox.pl (v1.10) Line: 94
root@otrs otrs/bin#
OK, obviously something is wrong with that file.
root@otrs otrs/bin# ls -l /usr/share/otrs/Kernel/Config/Files/Z*
lrwxrwxrwx 1 root root 32 Jun 30 03:24
/usr/share/otrs/Kernel/Config/Files/ZZZAAuto.pm ->
/var/lib/otrs/Config/ZZZAAuto.pm
lrwxrwxrwx 1 root root 31 Jun 30 03:24
/usr/share/otrs/Kernel/Config/Files/ZZZAuto.pm ->
/var/lib/otrs/Config/ZZZAuto.pm
root@otrs otrs/bin#
OK this looks like where I was last week when I bricked the machine.
Lets look at the targets of these links.
root@otrs otrs/bin# ls -l /var/lib/otrs/Config/
total 120
-rw-rw-r-- 1 root www-data 119182 Jun 30 04:46 ZZZAAuto.pm
root@otrs otrs/bin#
Definitely where I bricked the machine last week.
I made the mistake of touching the missing target and then chmod & chown to
match the target that IS there.
If I do that again, Ill likely render the web interface unuseable again and
even if I back out my change, I STILL
Wont be able to run the web interface. Once its clobbered, it stays
clobbered.
OK, so I don't shoot myself in the foot with a cannon, what is the RIGHT way
to solve this ?
Wasn't the machine supposed to have created this file by itself ?
From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of
Muhammad El-Sergani
Sent: Thursday, June 30, 2011 2:25 PM
To: User questions and discussions about OTRS.
Subject: Re: [otrs] Bricked install
Hello Robert,
Thanks for taking the time and getting back to my question.
Allow me to be frank, but I'm not 100% in compliance with what you just
said. You're correct though about hell when one has to chase some
fairy-dependency for some RPM to be installed... for that you've got YUM,
and oh boy, it really does the job, believe me.
To be quite honest with you, I don't know what tasks you need done with your
Linux server, this specific server I mean, but if you ask me, it's best to
deploy OTRS alone, or along some other light-weight production/testing
software that you need, unless the server is too powerful anyway.
I've got many servers to administer, and I have to tell you this, I
personally recommend CentOS every time a new server is bought and deployed,
and my installations run pretty smoothly every single time. I run OpenSuse
and it's pretty good as well, but I believe more in CentOS.
To answer your questions:
1) Almost ALWAYS building from source works for me, and I believe I speak
for the Linux community when I say so... gosh I don't wanna say that
building from source is always better for me, I feel the app was
specifically built to run on my particular machine's environment
2) You could do the same by building your own RPM from the source code..
it's easy, google rpm-build, or email me
3) Please bear in mind that there are over 200 known Linux distros, there is
no way anyone will sit down and build RPMs or DEBs (or who knows what else)
for one software for everyone out there... RPMs where built for the widely
used OS's.. not to mention, the originally founder and developer of OTRS is
an ex-Suse, which is RPM-based :)
One last thing before you decide upon which road you want to take, I reckon
you shouldn't be mentioning that you might lose interest in OTRS if you fail
to deploy it easily, and that there's better hope in that other MS product.
I mean come on, even OTRS users over Windows know they're hugely mistaken ;)
In my opinion, dedicate time and server resources to a fresh CentOS
installation proceed with an RPM, if you really need the server to be up and
running OTRS quickly. Otherwise, take the longer road, do some research and
build from source, it'll be your custom-made package.
P.S. We're all sysadmins, we don't have time to develop, it's not our job...
our job is to search for the best adequate solution, grab it, learn (2 lines
below that :) ) how to deploy and use it and carry on searching for good
tools that we need for our daily tasks :)
Hope you don't find any of the above offensive, none intended :)
Thanks and Best Regards,
Muhammad El-Sergani.
On Thu, Jun 30, 2011 at 5:28 PM, Robert Woodworth
Mixture of resultrs.Ive now lost count how many times Ive wiped the machine and started from scratch. I finally found the missing piece of sasl, so now I can send mail from the otrs box Turnkey OTRS seems to be a genuine but very lean Ubuntu 10.04 OS. The newest .deb out there for OTRS is 2.4.7 so that's what Im running. While I can now send mail to otrs, Im still not receiving yet.Because the 2.4 docs don't accurately explain 2.4.7, Im having to guess a lot. Im still in the race to see if I can get a system into production before the Microsoft group can. Right now, Im using the otrs postmaster system from the otrs cron. SHOULD I be DOING THIS ? Or should I just punt and set up fetchmail ? If I don't get mail coming on to the machine, the rest is moot. Yes I know I should be running 3.0 or above, but there aren't any debs for it yet so Im stuck with 2.4.7 Suggestions how to get mail on to the machine ?
-- Thanks and Best Regards, Muhammad El-Sergani. --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs