Am 02.02.2016 um 10:06 schrieb snielson:
>
> Hello everyone,
>
> I've rewritten dsapp (bash) into dsapp (python), and have dubbed it
> version 228.
> This is a pre-release, and was hoping I can get some input / reports on
> any issues found with it.

1. Health check reports:

==========================================================
Checking Database Schema..
==========================================================
Schema version: 14.2.0.279Mobility version: 14.2.0.279

Version mismatch between mobility and schema
Suggestion: Run /opt/novell/datasync/update.sh to update the schema

Failed

False alarm as I see...

2. after database maintenance the deamons won´t start
note: using gms 14.2.0

3. Checking users FDN..
==========================================================
Invalid FDN: ganger.ef-po1.ef-dom1

what´s to do here? At other places you point to a TID.

HTH
Gotthard



--
Gotthard Anger
Anwenderbetreuung Netzwerkadministration
Landeskirchenamt der EKM
gotthardanger@no-mx.forums.novell.com
http://forums.novell.com/member.php?u=35038

Mails an diese Adresse werden nur nach vorheriger Ansage gelesen!
Mails for this address will only be read if you trigger me before.

Gotthard Anger;2419311 wrote:
Am 02.02.2016 um 10:06 schrieb snielson:
>
> Hello everyone,
>
> I've rewritten dsapp (bash) into dsapp (python), and have dubbed it
> version 228.
> This is a pre-release, and was hoping I can get some input / reports on
> any issues found with it.
>
>1. Health check reports:
>
>==========================================================
>Checking Database Schema..
>==========================================================
>Schema version: 14.2.0.279Mobility version: 14.2.0.279
>
>Version mismatch between mobility and schema
>Suggestion: Run /opt/novell/datasync/update.sh to update the schema
>
>Failed
>
>False alarm as I see...
>
>2. after database maintenance the deamons won´t start
>note: using gms 14.2.0
>
>3. Checking users FDN..
>==========================================================
>Invalid FDN: ganger.ef-po1.ef-dom1
>
>what´s to do here? At other places you point to a TID.
>
>HTH
>Gotthard
>
>
>
--
Gotthard Anger
Anwenderbetreuung Netzwerkadministration
Landeskirchenamt der EKM
gotthardanger@no-mx.forums.novell.com
http://forums.novell.com/member.php?u=35038

Mails an diese Adresse werden nur nach vorheriger Ansage gelesen!
Mails for this address will only be read if you trigger me before.

Hi Gothhard,

All three of those issues should be fixed in dsapp 229
https://github.com/snielson/dsapp_python/releases/tag/2.00-229

Let me know if you still have issues with them after the upgrade.

Hi,

Am 09.02.2016 um 17:36 schrieb snielson:
>
> All three of those issues should be fixed in dsapp 229
> https://github.com/snielson/dsapp_py...s/tag/2.00-229
>
> Let me know if you still have issues with them after the upgrade.
>
All complained issues were fixed in 229
Last issue (not new, but investigated):
Checking Sever Date.. Failed

Time check is fixed to our own time server, servers in internet are not
reachable
so your test to time.nist.gov must be fail.
==========================================================
Checking Sever Date..
==========================================================
Failure with NTP server: time.nist.gov

Local server date:
Year: 16
Month: 2
Day: 11

No response from 'time.nist.gov'

Can you read the actual time server from system configuration?

Go



--
Gotthard Anger
Anwenderbetreuung Netzwerkadministration
Landeskirchenamt der EKM
gotthardanger@no-mx.forums.novell.com
http://forums.novell.com/member.php?u=35038

Try changing the timeserver in /opt/novell/datasync/tools/dsapp/conf/setting.cfg

[GHC]
ntp.server = time.nist.gov

Note: Not all ntp servers respond with a proper time or format

You can also disable the date check in /opt/novell/datasync/tools/dsapp/conf/ghc_checks.cfg
Change
server.date = True
to
server.date = False

The reason I default get time from a outside source is to verify the date is correct (for the next check : certificate expiry date)
If that date is incorrect on your ntp server, and GMS server is set from that.. the check would pass (Even if the date was actually wrong)

Try changing the timeserver in /opt/novell/datasync/tools/dsapp/conf/setting.cfg

[GHC]
ntp.server = time.nist.gov

Note: Not all ntp servers respond with a proper time or format

You can also disable the date check in /opt/novell/datasync/tools/dsapp/conf/ghc_checks.cfg
Change
server.date = True
to
server.date = False

The reason I default get time from a outside source is to verify the date is correct (for the next check : certificate expiry date)
If that date is incorrect on your ntp server, and GMS server is set from that.. the check would pass (Even if the date was actually wrong)

Am 11.02.2016 um 18:46 schrieb snielson:
>
> Try changing the timeserver in
> /opt/novell/datasync/tools/dsapp/conf/setting.cfg
>
> [GHC]
> ntp.server = time.nist.gov
works.
>
> Note: Not all ntp servers respond with a proper time or format
> The reason I default get time from a outside source is to verify the
> date is correct (for the next check : certificate expiry date)
> If that date is incorrect on your ntp server, and GMS server is set from
> that.. the check would pass (Even if the date was actually wrong)
Which system can I trust if not a ntp server?
It would be a nice check to see if the used time server has wrong time
in comparision to time.nist.gov.

But in fact, my gms can´t connect to the internet. So your additional
settings regarding to novell.com must fail in my case.

From my own (bad) expierience I would recommend to add a test, if there
a proxy setting exist and eventually enabled. Should result in first
case in yellow, second case in red :-)

BTW: the detection of nightly maintenance is working now, I remember for
an discussion one year ago...

Go





--
Gotthard Anger
Anwenderbetreuung Netzwerkadministration
Landeskirchenamt der EKM
gotthardanger@no-mx.forums.novell.com
http://forums.novell.com/member.php?u=35038

Mails an diese Adresse werden nur nach vorheriger Ansage gelesen!
Mails for this address will only be read if you trigger me before.