Ok, that seems to have worked!
I get logged in with my old username and password. It looks good so
far - though I have not yet tested functionality.
A quick question - is the old crontab still valid?
Or do I have to redo it all?
--
“Don't eat anything you've ever seen advertised on TV”
> Message: Can't remove shm for log: Operation not permitted
On the German list a fellow hit upon this error and reports that it
worked fine when he ran it as root
So I'm going to restore my DB and try again with this in mind.
Will keep you posted
--
“Don't eat anything you've ever seen adver
Crumb!
I may just bite the bullet and do a fresh install. Since I have not
yet deployed, I have that option. And it may be a good way for me to
learn the system better anyway.
On Thu, Jul 30, 2009 at 8:49 AM, Michiel Beijen wrote:
> Alan,
>
> Actually, I don't understand where the error messag
Alan,
Actually, I don't understand where the error message you get, "Message:
Can't remove shm for log: Operation not permitted" comes from. I understand
that OTRS tries to do a Kernel::System::Log Cleanup () but why it can't do
that, beats me.
If there is anyone other who'd like to help you with
Any further comment on the below? Or am I going to have to back out
of my upgrade?
On Wed, Jul 29, 2009 at 12:53 PM, Alan McKay wrote:
>> Did you put the new files of 2.4.2 in the 2.3.4 directory?
>
> Yes, that's what you told me to do, no?
> What I actually did was create another symlink from /o
> Did you put the new files of 2.4.2 in the 2.3.4 directory?
Yes, that's what you told me to do, no?
What I actually did was create another symlink from /opt/otrs-2.4.2 to
/opt/otrs-2.3.4, because the tarball has the directory name
"otrs-2.4.2" built into it. So I copied the tarball to /opt, cd
What struck me is this:
Bad address at /opt/otrs-2.3.4/Kernel/System/
>
> Log.pm line 230.
>
> Did you put the new files of 2.4.2 in the 2.3.4 directory? The name 2.3.4
triggers me here...
- Are you the otrs user? It seems you don't have permission on the shared
memory used for the log file.
--
Mi
Nope, I ran set permissions and same problem
--
“Don't eat anything you've ever seen advertised on TV”
- Michael Pollan, author of "In Defense of Food"
-
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http:
Yikes!
*) Run the migration script (as OTRS user, _not_ as root):
You must execute the migration script to migrate some data from the
old database
structure to the new one. Please run $OTRS_HOME/scripts/DBUpdate-to-2.4.pl!
I think my problem is that this step actually has to come first :
*
Yup. Of course, then you'd have files that are removed from OTRS since 2.3.4
still in your installation. But I guess it is the best you could do and it
would work.
(please don't forget to follow the other steps from UPGRADING such as the
database update)
But if anyone has a better idea, I'd be ope
> The trick of "just point the symlink to the new version" does not work with
> OTRS as this inconveniently does NOT keep its configuration files in /etc
So what about this?
I will backup (re-tar) /opt/otrs-2.3.4, and then remove the symlink,
and rename it to /opt/otrs
Then untar the the new 2.4
Hi Allan,
Well, if you had an installation from source there will be no OTRS services
running; I guess you could stop apache and perhaps the cron jobs.
The trick of "just point the symlink to the new version" does not work with
OTRS as this inconveniently does NOT keep its configuration files in
On Wed, Jul 29, 2009 at 8:05 AM, Michiel Beijen wrote:
> http://source.otrs.org/viewvc.cgi/otrs/UPGRADING?revision=1.35&view=co
Hmmm, I'm stuck on the very first step
*) Stop all your services (e. g. rcotrs stop-force)
I did not know there were any services running! And I don't see any.
And do
Hi Alan,
Of course you can upgrade your existing installation!
Follow the steps you find here:
http://source.otrs.org/viewvc.cgi/otrs/UPGRADING?revision=1.35&view=co
As you might have noticed; 2.4.2 is just released, fixing a couple of bugs
in 2.4.1; you might go with that.
Kindest regards,
--
On Tue, Jul 28, 2009 at 1:21 PM, Martin Edenhofer wrote:
> In OTRS 2.4 there is a new frature called "Configurable event based
> notifications".
OK, since I have not yet deployed this thing, I have a good
opportunity now to upgrade.
Is there an upgrade wizard of some sort that will leave me with
15 matches
Mail list logo
