Hi,
I would add a field to the tickets, it wanted to take freetext or freekey. That
field would show a dropdown with the areas that my company has.
Un saludo
Carlos Guerra
Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si no
i dont tried this yet but the problem is not if a third step can fix the
first login. the problem is that the default setup in a clean installation
is not working as usual. Alan McKay has make the same post with the same
problem with the subject OTRS 2.4.2 first login
I've upgrade yesterday the
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
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”
Is there any way to force a survey send? Anyway to increase the
debugging level? Are any files created during the survey process and
where do they go? What does a good survey trigger look like in otrs.log?
Walter R. Moore wrote:
I have *increased* Survey::SendPeriod: from 0 to 0.0001, but it is
Unfortunately the Windows installer currently suffers of a broken PPM
(and a broken cpan module as well). Please see this bug report:
http://bugs.otrs.org/show_bug.cgi?id=3789
A workaround is included in the report.
Also, in OTRS v 2.3.3 and up, Mail::POP3Client and IO::Socket::SSL are
used for
As soon as I click the new dashboard link :-(
Software error:
Can't use an undefined value as an ARRAY reference at
/opt/otrs//Kernel/System/Ticket/IndexAccelerator/RuntimeDB.pm line
210.
For help, please send mail to the webmaster (supp...@recognia.com),
giving this error message and the time
What do these return?
perl -cw /opt/otrs/bin/cgi-bin/index.pl
perl -cw /opt/otrs/bin/PostMaster.pl
--
“Don't eat anything you've ever seen advertised on TV”
- Michael Pollan, author of In Defense of Food
-
OTRS
On Fri, Jul 31, 2009 at 9:36 AM, Aquiles Cohenaqco...@gmail.com wrote:
i dont tried this yet but the problem is not if a third step can fix the
first login. the problem is that the default setup in a clean installation
is not working as usual. Alan McKay has make the same post with the same
Hi Alan,
it seems that you do not have a standard installation. It looks that
you did some changes in SysConfig regarding viewable 'lock' settings.
Please be care with this kind of setting. Only change it if you know
what you are doing.
You have IMO 2 possible ways.
a) Remove all your
it seems that you do not have a standard installation. It looks that you did
some changes in SysConfig regarding viewable 'lock' settings.
I have not made any changes in the area of viewable locks.
I don't even know what that is.
But I can return the given files to their defaults to see what
OK, in Kernel/Config.pm the only changes I have are to configure the
DB, and also these (I've removed their actually values) :
# $DIBI$
$Self-{'FQDN'} =
$Self-{'HttpType'} =
$Self-{'AdminEmail'} =
$Self-{'Organization'} =
And that ZZZAuto file looks like this (some values
Hi Alan,
On Jul 31, 2009, at 17:08 , Alan McKay wrote:
it seems that you do not have a standard installation. It looks
that you did
some changes in SysConfig regarding viewable 'lock' settings.
I have not made any changes in the area of viewable locks.
I don't even know what that is.
But
PS: It would be glad if you post your questions only on one list. Many
thanks for that!
OK, sorry. It appeared to me as though there were different experts
on each list so it seemed to make sense.
I'll stick with english for this problem, then.
--
“Don't eat anything you've ever seen
Hi Alan,
does the line 210 read:
. ti.ticket_lock_id NOT IN ( ${\(join ', ', @{$Self-{ViewableLockIDs}})}
)
-- because that was in 2.3.4
-- What is the file revison?
Please check the file from:
does the line 210 read:
. ti.ticket_lock_id NOT IN ( ${\(join ', ', @{$Self-{ViewableLockIDs}})}
. ar.ticket_id = ti.id AND
-- What is the file revison?
# --
# Kernel/System/Ticket/IndexAccelerator/RuntimeDB.pm - realtime database
# queue ticket index module
# Copyright (C)
On Thu, Jul 30, 2009 at 10:44 AM, Alan McKayalan.mc...@gmail.com wrote:
Hey folks,
I wiped my DB and started over, and am to the point in the install
where I am testing the first login.
The instructions for 2.4.2 are the same as 2.3.4 and say to use
r...@localhost and root, but that is not
Hi Alan,
On Jul 30, 2009, at 17:23 , Alan McKay wrote:
roK20XGbWEsSM
I'll remove it and see what happens
I have phpPGadmin running and could use it to set the PW. But
googling is not helping me.
Just removing will not help. You need to set it.
Just use
shell bin/otrs.setPassword
This would seem to be my base issue. BTW, I'm using Postgres. And I
did manage to get this working just fine on 2.3.4
-bash-3.2$ bin/otrs.setPassword r...@localhost root
DBD::Pg::st execute failed: ERROR: permission denied for relation
users at /opt/otrs-2.4.2/Kernel/System/DB.pm line 559.
On Fri, Jul 31, 2009 at 12:23 PM, Alan McKayalan.mc...@gmail.com wrote:
This would seem to be my base issue. BTW, I'm using Postgres. And I
did manage to get this working just fine on 2.3.4
OK, I did this :
otrs=# GRANT ALL PRIVILEGES ON DATABASE otrs to otrs;
And I still have the issue.
Hi Alan,
On Jul 31, 2009, at 18:23 , Alan McKay wrote:
This would seem to be my base issue. BTW, I'm using Postgres. And I
did manage to get this working just fine on 2.3.4
-bash-3.2$ bin/otrs.setPassword r...@localhost root
DBD::Pg::st execute failed: ERROR: permission denied for
It looks really like an database permission problem. I'm not a postgres
guru, so I do not know how to grand this permissions in postgresql. :-/
See my follow up - I granted them and still no go.
And I'm no DB guru either - and my DB Admin is away on vacation.
I think he is back next week so
OK, I just went into
psql otrs
And did \d to show all tables.
They were all still owned by user postgres, so I did this to change
them all to owner otrs
first I just did
psql otrs -c \d somefile
Then edited somefile to remove headers and footers
cat somefile | awk '{print $3}' otherfile
Hi Alan,
On Jul 31, 2009, at 21:06 , Alan McKay wrote:
OK, I just went into
psql otrs
And did \d to show all tables.
They were all still owned by user postgres, so I did this to change
them all to owner otrs
first I just did
[...]
psql otrs -c ALTER TABLE $table OWNER TO otrs;
done
And it
Fine! :) Also all the other stuff like dashboard?
I'm not that far yet - doing many different things at once
Will keep you posted.
I got logged in OK.
[...]
OK, dashboard does not crash at least - so that seems to be a good start :-)
--
“Don't eat anything you've ever seen advertised on
Hi all, I just upgraded to otrs 2.4.2 and escalated ticket have
strange time values: in dashoboard view, time shown is like 344960
hours and 50 mins or other values like this...
Any ideaa?
Thx,
Diego
This message was sent
Hi Diego,
On Jul 31, 2009, at 23:57 , diego.giardine...@zephirworks.com wrote:
Hi all, I just upgraded to otrs 2.4.2 and escalated ticket have
strange time values: in dashoboard view, time shown is like 344960
hours and 50 mins or other values like this...
Also after rebuilding the
Problem solved, thx!
Diego
Def. Quota Martin Edenhofer m...@otrs.com:
Hi Diego,
On Jul 31, 2009, at 23:57 , diego.giardine...@zephirworks.com wrote:
Hi all, I just upgraded to otrs 2.4.2 and escalated ticket have
strange time values: in dashoboard view, time shown is like 344960
hours
Hi Renée
Super! Danke funktioniert.
Grüße
Nicola
Am 30.07.2009 um 17:41 schrieb Renee Bäcker:
Hallo Nicola,
Nicola Tiling schrieb:
OpenNMS meldet mir:
2009-03-22 00:10:55,228 DEBUG [OpenNMS.TroubleTicketer]
EventIpcManagerDefaultImpl: In ListenerThread
OpenNMS.TroubleTicketer run
Ich werde ab 31.07.2009 nicht im Büro sein. Ich kehre zurück am
03.08.2009.
Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.
In dringenden Fällen wenden Sie sich bitte an Herrn Hildebrandt unter
05651-306-8510 bzw. Herrn Uwe Mark 05651-306-8512.
Bei technischen Probleme oder
Hi,
*snip*
Sobald ich dies aber ausführe lande ich in folgendem Fehler:
~$ scripts/DBUpdate-to-2.3.pl
Start migration of the system...
*snip*
jetzt tuts :)
Man Merke das die Config.pm von 2.2.4-1 zu 2.3.4 nicht kompatibel ist.
Macht am besten nen Vimdiff und fügt die Änderungen in die neue
Hallo,
Wenn ich im Firefox den Cookie lösche vom OTRS, funktioniert OTRS im Firefox.
OTRS funktioniert nur solange im Firefox, bis man sich abmeldet oder man sich
neu enmeldne möchte. Dann zeigt Firefox nur den Quellcode an wieder. Nach
löschen des Cookies geht es wieder.
With best regards
Liebe liste,
ich habe ein paar ideen für otrs...
in der druckansicht zum ticket wir auch die ticket-nummer als barcode
mitangegeben. (somit kann ich im supportfall die ticketnummer auch gleich
öffnen bzw suchen)
zb: so
In der Doku zu 2.4 steht:
New Management Dashboard
- Integration of RSS
im otrs_admin_book.pdf steht auf Seite 281:
DashboardBackend###0100-RSS
aber was das genau macht findet sich nirgendwo.
Kann man damit RSS Feeds GENERIEREN oder einen RSS Fedd von irgendwo
ins Dashboard einbauen?
--
Ralf
* Ralf Hildebrandt ralf.hildebra...@charite.de:
Kann man damit RSS Feeds GENERIEREN oder einen RSS Fedd von irgendwo
ins Dashboard einbauen?
OK, man kann einen remote feed einbauen. Nett. Allerdings sind beim
heise RSS feed die Umlaute kaputt:
Heise News Schließen
Skype-Dienste wegen
Hi
Würde mich auch mal interessieren. denn auch beim Wechsel vom 2.3.4 zu
2.4.2 scheint sich hier nichts geändert zu haben. ich sehe jedenfalls
auch keine linke Navbar mit der Einstellung
Modern (Frontend::NavBarStyle in Framework - Frontend::Agent)
Grüsse
Nicola
bin nach einigen
Und du hast dann am Anfang das neue 2.4.2 tarball innerhalb vom 2.3.4
Verzeichnis ungetarrt?
--
“Don't eat anything you've ever seen advertised on TV”
- Michael Pollan, author of In Defense of Food
-
OTRS mailing
* Alan McKay alan.mc...@gmail.com:
Und du hast dann am Anfang das neue 2.4.2 tarball innerhalb vom 2.3.4
Verzeichnis ungetarrt?
Genau so.
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benjamin Franklin
Hindenburgdamm 30 |
OK, es scheint erfolgreich geupgraded zu werden. Mal gucken, wie es
jetzt funktioniert.
Danke Ralf.
Noch eine kleine frage - gilt noch das alte crontab von 2.3.4?
--
“Don't eat anything you've ever seen advertised on TV”
- Michael Pollan, author of In Defense of Food
* Alan McKay alan.mc...@gmail.com:
OK, es scheint erfolgreich geupgraded zu werden. Mal gucken, wie es
jetzt funktioniert.
Danke Ralf.
Noch eine kleine frage - gilt noch das alte crontab von 2.3.4?
Die habe ich nicht angefasst, allerding ist das ja nun ein winziger
Teil.
Auf den ersten
Diese zwei:
$HOME/bin/GenericAgent.pl -c db /dev/null
und
$HOME/bin/GenericAgent.pl /dev/null
scheinen dasselbe Problem zu haben - aber welches?
- Forwarded message from Cron Daemon mailadre...@charite.de -
Date: Fri, 31 Jul 2009 16:20:03 +0200 (CEST)
Subject: Cron o...@otrs
Sobald wie ich auf der Dashboard-linke klicke :-(
Software error:
Can't use an undefined value as an ARRAY reference at
/opt/otrs//Kernel/System/Ticket/IndexAccelerator/RuntimeDB.pm line
210.
For help, please send mail to the webmaster (supp...@recognia.com),
giving this error message and the
* Ralf Hildebrandt ralf.hildebra...@charite.de:
Diese zwei:
$HOME/bin/GenericAgent.pl -c db /dev/null
und
$HOME/bin/GenericAgent.pl /dev/null
scheinen dasselbe Problem zu haben - aber welches?
- Forwarded message from Cron Daemon mailadre...@charite.de -
Date: Fri, 31 Jul 2009
Hi Alan,
es sieht so aus, also ob Du keine Standard Installation hast. Es sieht
so aus, als ob Du verschiedene Einstellungen bezüglich 'viewable
locks' in SysConfig geändert hast.
Bitte mache solche Änderungen nur, wenn Du weiß was Du machst.
IMO hast Du nun zwei Möglichkeiten das zu
Hi Alan,
it seems that you do not have a standard installation. It looks that
you did some changes in SysConfig regarding viewable 'lock' settings.
Please be care with this kind of setting. Only change it if you know
what you are doing.
You have IMO 2 possible ways.
a) Remove all your
On Fri, Jul 31, 2009 at 11:02 AM, Martin Edenhoferm...@otrs.com wrote:
Hi Alan,
es sieht so aus, also ob Du keine Standard Installation hast. Es sieht so
aus, als ob Du verschiedene Einstellungen bezüglich 'viewable locks' in
SysConfig geändert hast.
Bitte mache solche Änderungen nur, wenn
Hi Alan,
On Jul 31, 2009, at 17:06 , Alan McKay wrote:
es sieht so aus, also ob Du keine Standard Installation hast. Es
sieht so
aus, als ob Du verschiedene Einstellungen bezüglich 'viewable
locks' in
SysConfig geändert hast.
Bitte mache solche Änderungen nur, wenn Du weiß was Du machst.
Hallo Ralf,
ich hatte das gleiche Problem und hatte es als Bug gefiled.
Unter http://bugs.otrs.org/show_bug.cgi?id=3966 findest Du 2
Lösungsvorschläge. Den ersten (LDAP-Update) konnte ich nicht
durchführen, aber der 2. brachte die Lösung:
. commenting out Line 722-725 in
48 matches
Mail list logo
