Greetings,
I'm configuring a new 1.5.9 install. I tried to look for the answer in
the LedgerSMB manual but the manual from the website is for v1.3x... So.
Under "Security Settings"
Password Duration: Is this days? minutes? seconds? What is the default?
Suggestion #1:
Whatever the duration period is, place it next to the description along
with the default value. Like so:
Password Duration, in Days (Default=2 days):
Session Lockout: Is this minutes? seconds? What is the default?.
Suggestion #2:
Whatever the duration period is, place it next to the description along
with the default value. Like so:
Session Lockout, in Minutes (Default=10 minutes):
Suggestion #3 (for next release):
Enable the Sys Admin to disable the Password Duration altogether. So
setting the Password Duration to "0" means that user passwords do not
expire.
You could just replace the a "hard" password expiration with just a
180-day nag like this:
Your password is over 180 days old. Please consider replacing the
current password with a newer one.
And, include a link/button that says: "Disregard". Which will stop the
nag for another 180 days.
Thanks!
Regards,
Michael
--
======================
Michael Chinn
Miguel.Chinn(a)Gmail.com
~ ~~ ~ ~ o:)^))>~< <;)^)))>~<
~ ~ ~~ ~ <:)^)))>~< <;)^)>~<
~~ ~~~ ~ ~ ~ o:)^)))>-< <;)^))>~<
~ ~~ ~~ ~~ ~ o;)^))>-< <:)^))>~<
~~ ~ ~o:)^))>~<
Greetings:
Version: 1.5.9
Environment: Ubuntu-16.04 x64
Apache2 + PostgreSQL-9.5
Following install instructions at:
https://ledgersmb.org/content/installing-ledgersmb-15
Got all the way to the "setup.pl". Enter the user name "lsmb_dbadmin" +
password + name-of-new-company-db.
Got this error:
Error!
APPLICATION ERROR at
/usr/local/share/perl/5.22.1/PGObject/Util/DBAdmin.pm line 265.
dbversion: 1.5.9, company:
Status: 500 Internal server error (PSGI.pm run_new)
I've checked Apache2, Starman, and PostgreSQL and all are up and running
w/o errors.
Help? Hints?
Regards,
Michael
--
======================
Michael Chinn
Miguel.Chinn(a)Gmail.com
~ ~~ ~ ~ o:)^))>~< <;)^)))>~<
~ ~ ~~ ~ <:)^)))>~< <;)^)>~<
~~ ~~~ ~ ~ ~ o:)^)))>-< <;)^))>~<
~ ~~ ~~ ~~ ~ o;)^))>-< <:)^))>~<
~~ ~ ~o:)^))>~<
On Sun, Aug 13, 2017 at 7:05 PM, Robert J. Clay <rjclay(a)gmail.com> wrote:
> Note that this version does not include ledgersmb-1.5-apache for
> the Apache proxy configuration as there was still an issue with that
A test package of ledgersmb-1.5 that does include the problem
ledgersmb-1.5-apache deb was also uploaded to our apt repository last
night. That's in 'test' instead of 'main' and is version 1.5.9-2~1.
That's also associated with the temporary branch 'dev/ApacheProxy' at
https://github.com/ledgersmb/pkg-ledgersmb-1.5, as well as the open
issue https://github.com/ledgersmb/pkg-ledgersmb-1.5/issues/2.
At our apt package repository in 'test', for 'stretch':
ledgersmb-1.5_1.5.9-2~1_all.deb
ledgersmb-1.5-apache_1.5.9-2~1_all.deb
ledgersmb-1.5-nginx_1.5.9-2~1_all.deb
I emphasize that this is only a test version (and may not end up
being the only one, depending on how the troubleshooting goes) for an
issue with the apache proxy configuration associated with the
legdersmb-1.5-apache package. Once that issue has been resolved, it
will be released in a new non-test version.
--
Robert J. Clay
rjclay(a)gmail.com
jame(a)rocasa.us
4096/198CAB6F43B7EA9A
The initial version of the debian pkg for legdgersmb-1.5, version
1.5.9-1, has been released and uploaded to our apt package repository
for 'main' in stretch. It has also been uploaded to our PPA, for
artful (the future v17.10).
Note that this version does not include ledgersmb-1.5-apache for
the Apache proxy configurtion as there was still an issue with that
but does include ledgersmb-1.5-nginx for the Nginx proxy
configuration.
At our apt package repository:
ledgersmb-1.5_1.5.9-1_all.deb
ledgersmb-1.5-nginx_1.5.9-1_all.deb
At our PPA:
ledgersmb-1.5_1.5.9-1~ubuntu17.10.1_all.deb
ledgersmb-1.5-nginx_1.5.9-1~ubuntu17.10.1_all.deb
--
Robert J. Clay
rjclay(a)gmail.com
jame(a)rocasa.us
4096/198CAB6F43B7EA9A
Hi,
I would like to suggest you make the mailing list subject tag include
the words ledger smb in it? something like [ledger-smb-users] for instance.
this would make it clearer for people who are subscribe to many mailing
lists.
Thanks
Jason
--
Jason Lewis
http://emacstragic.net
I should have sent our conversations to the public mailing list. Forwarding
there now.
Regards, Erik
---------- Forwarded message ----------
From: "Erik Huelsmann" <ehuels(a)gmail.com>
Date: Aug 7, 2017 21:37
Subject: Re: [users] LedgerSMB Docker image doens't start /compile
To: "Stefan Mueller" <stefan.mueller.83(a)gmail.com>
Cc:
Hi Stefan,
On Mon, Aug 7, 2017 at 6:56 PM, Stefan Mueller <stefan.mueller.83(a)gmail.com>
wrote:
> I've just tried in Kitematic:
> stopping anything
> open CLI
>
> PS C:\Program Files\Docker\Docker> docker run --name some-postgres -e
> POSTGRES_PASSWORD=test -d postgres
> 0e58fe4f981692498f5e626cf7357e46d71c3d2e056d6262c3969bda462ac849
> docker run --name myledger --link some-postgres:postgres -d
> ledgersmb/ledgersmb
> b32c16a9debdd57578d1213229b01c01bd2db49b743d4e0bb811dc8d4077e96d
>
> started postgres docker image
> started ledgersmb docker image
>
By this time, were the docker and postgres images not already running? I
think you should be starting the 'some-postgres' and the 'myledger' images.
> opened
> http://192.168.99.100:32771/setup.pl
>
> lsmb_dbadmin and postgres are avaible as presets but neither mysecretpassword
> nor postgres nor test is working
>
>
That's unexpected. I would have expected that you would need to connect to
http://192.168.99.100:5762/setup.pl (or some other IP address, but at least
that port).
I noted that I responded to you privately, but I should have done so
publicly on the mailing list. Would you mind moving back? That both
provides you with more resources which could provide you with an answer as
well as records our collective (developing) knowledge for others to read in
the mail archives.
Regards,
Erik.
> 2017-08-06 22:22 GMT+02:00 Stefan Mueller <stefan.mueller.83(a)gmail.com>:
>
>> I did a fresh start, so Docker downloaded the image from scratch. All
>> what I did, was pressing the start button and I don't see postgres image
>> running
>>
>> 2017-08-06 22:15 GMT+02:00 Erik Huelsmann <ehuels(a)gmail.com>:
>>
>>> Hi,
>>>
>>> On Sun, Aug 6, 2017 at 10:10 PM, Stefan Mueller <
>>> stefan.mueller.83(a)gmail.com> wrote:
>>>
>>>> yeah it works but how to I login as admin, it's lsmb_dbadmin and ???
>>>>
>>>
>>> Actually, as you probably created the PostgreSQL container with this
>>> argument:
>>>
>>> -e POSTGRES_PASSWORD=mysecretpassword
>>>
>>> You can use the 'postgres' user as the admin user and <mysecretpassword>
>>> as the password for postgres. That should let you into setup.pl.
>>>
>>>
>>>
>>> HTH,
>>>
>>>
>>> Erik.
>>>
>>>
>>>
>>> --
>>> Bye,
>>>
>>> Erik.
>>>
>>> http://efficito.com -- Hosted accounting and ERP.
>>> Robust and Flexible. No vendor lock-in.
>>>
>>
>>
>
--
Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
Hallo
I installed Docker Toolbox on Windows
<https://docs.docker.com/toolbox/toolbox_install_windows/> and trying to
run the Docker imager but if fails to start.
I can run postgres and nginx
<https://docs.docker.com/docker-for-windows/#explore-the-application-and-run…>
but
LedgerSMB fails with:
maybe: /usr/lib/perl5
Selected PERL5LIB=/usr/lib/perl5
mkdir: cannot create directory '/tmp/ledgersmb': File exists
Error while loading /srv/ledgersmb/tools/starman.psgi:
==============================================================================
== Running a Web Service as root is a security problem
== If you are starting LedgerSMB as a system service
== please make sure that you drop privlidges as per README.md
== and the example files in conf/
== This makes it difficult to run on a privlidged port (<1024)
== In theory you can pass the --user argument to starman,
== However starman drops privlidges too late, starting us as root.
==============================================================================
at /srv/ledgersmb/tools/../lib/LedgerSMB/Sysconfig.pm line 469.
Compilation failed in require at
/srv/ledgersmb/tools/../lib/LedgerSMB/App_State.pm line 9.
BEGIN failed--compilation aborted at
/srv/ledgersmb/tools/../lib/LedgerSMB/App_State.pm line 9.
Compilation failed in require at
/srv/ledgersmb/tools/../lib/LedgerSMB/Setting.pm line 58.
BEGIN failed--compilation aborted at
/srv/ledgersmb/tools/../lib/LedgerSMB/Setting.pm line 58.
Compilation failed in require at
/srv/ledgersmb/tools/../lib/LedgerSMB/PGNumber.pm line 15.
BEGIN failed--compilation aborted at
/srv/ledgersmb/tools/../lib/LedgerSMB/PGNumber.pm line 15.
Compilation failed in require at /srv/ledgersmb/tools/../lib/LedgerSMB.pm
line 149.
BEGIN failed--compilation aborted at
/srv/ledgersmb/tools/../lib/LedgerSMB.pm line 149.
Compilation failed in require at
/srv/ledgersmb/tools/../lib/LedgerSMB/PSGI.pm line 19.
BEGIN failed--compilation aborted at
/srv/ledgersmb/tools/../lib/LedgerSMB/PSGI.pm line 19.
Compilation failed in require at /srv/ledgersmb/tools/starman.psgi line 13.
BEGIN failed--compilation aborted at /srv/ledgersmb/tools/starman.psgi line
13.
smtp configured.
--------------------------------------------------------------------------------
Docker configuration:
docker --version
Docker version 17.06.0-ce, build 02c1d87
docker-compose --version
docker-compose version 1.14.0, build c7bdf9e3
docker-machine --version
docker-machine.exe version 0.12.0, build 45c69ad
docker-machine ls
NAME ACTIVE DRIVER STATE URL SWARM
DOCKER ERRORS
default * virtualbox Running tcp://192.168.99.100:2376
v17.06.0-ce
Last night new LedgerSMB 1.5.9, LedgerSMB 1.5 and LedgerSMB latest images
were released on Docker Hub (https://hub.docker.com/u/ledgersmb/).
These images fix a performance regression caused by the size reduction
efforts of last month.
With these new images, response times were seen to improve by a factor of
10.
Please report your issues either on the development mailing list or
directly in GitHub at https://github.com/ledgersmb/ledgersmb-docker/issues
--
Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.