Greetings!Hello Team, upon configuring the docker command: docker-compose up, i did encounter the following error below:
Starting ledgersmb2019_postgres_1 ... errorERROR: for ledgersmb2019_postgres_1 Cannot start service postgres: network f3a4c456e824f5462dfdedcbb29d41668863f1540aded7bc5c3bd93c2cbec085 not foundERROR: for postgres Cannot start service postgres: network f3a4c456e824f5462dfdedcbb29d41668863f1540aded7bc5c3bd93c2cbec085 not foundERROR: Encountered errors while bringing up the project.PS C:\Windows\System32\ledgersmb2019>
For your kind assistance on how could i successfully run an instance of LSMB thru Docker image.
Warm Regards,/ITD/ Ryle.Msinc/ITDept
yes, sorry that is a typo: I meant http://192.168.1.118:5762/setup.pl
---------- Forwarded message ---------
From: bill Ott <billott(a)theotts.org>
Date: Thu, Mar 21, 2019 at 1:21 AM
Subject: Re: [ledgersmb-users] Fwd: Production Install, Networking and Setup
To: Xboxboy Mageia <xboxboy.mageia(a)gmail.com>
http://192.168.1.*188*:5762/setup.pl???? Did you mean http://192.168.1.
Email: Mailto:firstname.lastname@example.org <billott(a)theotts.org>
On 3/19/19 9:47 PM, Xboxboy Mageia wrote:
Sorry Bill: I meant to send it to the list :-0
Please see the network info I've added, in response to both Bill and Erik.
On Mon, Mar 18, 2019 at 6:45 PM Xboxboy Mageia <xboxboy.mageia(a)gmail.com>
> I was sick over Xmas, and since then business has been booming, only now
> can I have a second look. Thank you all for you help.
> On Thu, Jan 10, 2019 at 10:38 AM bill Ott <billott(a)theotts.org> wrote:
>> Running "brctl show" w/o/ the quotes on the VM's host will show you the
>> bridge and the interfaces that are connected to it. 'ifconfig" w/o the
>> quotes on the VM's host will show you the all of interfaces.
> brctl show
> bridge name bridge id STP enabled
> virbr0 8000:525400da324e yes
> enp5s0 is on 192.168.1.109
> lo is on 127.0.0.1
> virbr0 is on 192.168.122.1
> (sorry can't ssh in at the moment, let me know if you need all the details)
> Might help chasing down the problem.
>> Bill Ott
>> Home: 919-363-0031
>> Cell: 919-434-7589
>> Email: Mailto:email@example.com <billott(a)theotts.org>
>> Website: http://www.theotts.org
>> Profile: http://www.linkedin.com/in/wbott
>> On 1/9/19 5:21 PM, Erik Huelsmann wrote:
>> Ok, so the debian install went simply. I used debian 9 (Stretch), without
>>>> a GUI. 'ip addr' gives 192.168.1.101, which sounds right, as that's my lan,
>>> I then followed the instructions on https://apt.ledgersmb.org/index.html,
>>> but I installed version 1.5, and did not add the 'test component', I don't
>>> know what that means, sorry.
>>> I was able to add the DB admin user where the prompt comes up: Now do I
>>> need to reset/config mysql's root user and password also?
>>> So from my desktop I tried to access via firefox
>>> 192.168.1.101:5762/setup.pl, but it's unable to connect.
>> Ok. Are you able to ping that ip address from your desktop? That should
>> indicate if you should expect to be able to connect to the web server as
>> Yes, I can ping the debian VM with "ping 192.168.1.118"
> I can access the default debian apache web server at 192.168.1.118, but no
> luck with 192.168.1.188:5762/setup.pl
> I have a functioning fedora os VM on 192.168.1.107 with nextcloud working
>> I have the VM network set to bridged, networking is my downfall, and the
>>> other thing I suspect is that I need to open the firewall for the webserver.
>> Bridged sounds fine. quick question: Is the "eth0" (or enpXs0 with X a
>> number) network on the VM's host part of the bridge? If not, you probably
>> need to enable IP forwarding. Before we go that route, lets start by
>> checking you can 'ping' the address though. (And: can you ping the host
>> that the VM is running on?)
>> I can ping the host with "ping 192.168.1.109"
>>> All advice appreciated.
>> http://efficito.com -- Hosted accounting and ERP.
>> Robust and Flexible. No vendor lock-in.
>> users mailing firstname.lastname@example.org://lists.ledgersmb.org/mailman/listinfo/users
>> users mailing list
users mailing email@example.com://lists.ledgersmb.org/mailman/listinfo/users
Migrations have become considerably more controlled since the 1.5 release,
which introduces a smooth migration from 1.4.
As such migration paths do not exist for 1.1, 1.2 and 1.3, I'm eager to
learn if there are any users out there of these old versions, and, if
you're not migratiing, what's keeping you from doing so.
If you can't publicly respond to this inquiry, please mail me privately so
I can treat your information confidentially.
Thanks for your responses,
http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
I have forgot to thank you and the instructions that you have provided are proven working.Thank you again Erik.
From: "users-request(a)lists.ledgersmb.org" <users-request(a)lists.ledgersmb.org>
Sent: Sunday, January 13, 2019 4:00 AM
Subject: users Digest, Vol 20, Issue 6
Send users mailing list submissions to
To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to
You can reach the person managing the list at
When replying, please edit your Subject line so it is more specific
than "Re: Contents of users digest..."
1. Fwd: Debian packages for LedgerSMB (Robert J. Clay)
2. Re: Are there any subscribers using LedgerSMB versions older
than 1.4? (Erik Huelsmann)
3. Exchange rate (Erik Huelsmann)
4. Re: Are there any subscribers using LedgerSMB versions older
than 1.4? (Erik Huelsmann)
Date: Fri, 11 Jan 2019 18:07:59 -0500
From: "Robert J. Clay" <rjclay(a)gmail.com>
Subject: [ledgersmb-users] Fwd: Debian packages for LedgerSMB
Content-Type: text/plain; charset="UTF-8"
Forgot to cc this to the mailing list...
---------- Forwarded message ---------
From: Robert J. Clay <rjclay(a)gmail.com>
Date: Tue, Jan 1, 2019 at 2:16 PM
Subject: Re: [ledgersmb-users] Debian packages for LedgerSMB
To: Nicolas Couchoud <nicolas.couchoud__ledgersmb(a)normalesup.org>
On Mon, Dec 31, 2018 at 10:07 AM Nicolas Couchoud
> As far as I have understood, there are two sorts of Debian packages for
> LedgerSMB :
> * Debian regular repositories just contain packages called « ledgersmb » ;
Yes, that's the official Debian package for the LedgerSMB
application (which also migrates over to the developmental version of
Ubuntu). The most recent is the one for the most recently released
version of LedgerSMB, 1.6.9. (Released just a few days ago.)
> * your repository apt.ledgersmb.org contains packages with names like
> « ledgersmb-1.5 » and « ledgersmb-1.5-apache ».
Yes, the ledgersmb-1.5 packages are for the 1.5.x versions of
LedgerSMB, with the latest being v1.5.24 (just released a few days
ago). The ones like ledgersmb-1.5-apache are for web proxies if one
wants to use one. The 1.5.x versions will be supported by the project
until December of this year (2019) when it will see its End Of Life
for community support..
There are also the ledgersmb-1.6 packages, which are for the 1.6.x
versions of the LedgerSMB application (the current stable). It also
has the associated packages for a web proxy selection.
> So, I feel a bit lost... Is there one preferred sort of package ? Are
> some of these obsolete ?
The ledgersmb-1.5 packages aren't "obsolete" but they are for the
old-stable version of LedgerSMB (1.5.x), which as noted will see End
of Life in December 2019. (Whereas the 1.6.x versions are good for
LedgerSMB Community Support until December of 2021.) Their advantage
is that due to the availability of dependencies, the ledgersmb-1.5
packages can be backported to older versions of Debian (or Ubuntu)
than the ledgersmb-1.6 packages currently can be.
The primary difference between the 'ledgersmb' package and the
'ledgersmb-1.x' packages is that due to Debian Policy (regarding
embedded libraries), the ledgersmb packages uses the system installed
packages for the Dojo libraries while the ledgersmb-1.x packages use
the embedded versions of the Dojo libraries that are released with
each version of the LedgerSMB application.
Robert James Clay
Robert J. Clay
Date: Sat, 12 Jan 2019 00:30:59 +0100
From: Erik Huelsmann <ehuels(a)gmail.com>
To: Peeter Pärtel <peeter(a)sigma.ee>
Subject: Re: [ledgersmb-users] Are there any subscribers using
LedgerSMB versions older than 1.4?
Content-Type: text/plain; charset="utf-8"
On Fri, Jan 11, 2019 at 4:05 PM Peeter Pärtel <peeter(a)sigma.ee> wrote:
still on 1.2.26 as it is the last version where I can freely change all
> existing invoices. As mistakes happen or clients want some other
> description etc changes on them, this is really important to us.
Yes, you brought up that point before, I remember. Actually, you were not
the only one to bring it up -- I've got a few other contacts that would
really like this functionality to be re-introduced again. Some time back, I
went over the possibilities to do so with Chris and we found a way to
extend LedgerSMB 1.3+ to support both your use-case and still maintain
Chris's position about not deleting data (maintaining a full audit trail).
Unfortunately, the pipeline for 1.7 is very full at the moment and I'm not
likely to be able to address this idea and build it into 1.7 (as that
release is planned for this summer).
But as latest version of Debian where 1.2.26 works is Debian 8 and it's end
> of life is June 30th 2020 we are planning to move away from LedgerSMB to
> some other software. Already migrating some companies starting 2019 and
> rest is planned starting from 2020.
It's not that I'd like to encourage you to keep working on 1.2, but if you
want to keep working on 1.2, I think that version can be made to work on
Debian 9+ quite easily.
> If there has been any changes in allowing to change existing invoices
> (both parts and services), then it would be good to know before we have
> left completely.
Yes, there has been a change in allowing existing invoices to be changed in
the sense that the project now has a way to maintain full audit trail,
working COGS *and* allow the changed invoices. Which means we're no longer
against allowing it. The actual code to allow it though is yet to be
Thanks for taking the time to respond!