SiWapp versus Frontaccounting

Questions specific to SolydK Back Office
User avatar
Arjen Balfoort
Site Admin
Posts: 8720
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: SiWapp versus Frontaccounting

Postby Arjen Balfoort » 14 Oct 2014 07:18

Make sure your /etc/apt/sources.list looks like this:

Code: Select all

deb http://business.solydxk.com/production solydxk main upstream import
deb http://business-debian.solydxk.com/production solydxk main contrib non-free
deb http://business-debian.solydxk.com/security solydxk main contrib non-free
Then update:

Code: Select all

sudo apt-get update
Check SiWapp's version:

Code: Select all

solydxk@solydxk ~ $ apt policy solydkbo-siwapp
solydkbo-siwapp:
  Installed: 1.0.7
  Candidate: 1.0.7
  Version table:
 *** 1.0.7 0
        500 http://business.solydxk.com/production/ solydxk/main amd64 Packages
        100 /var/lib/dpkg/status
Before you re-install, you can try re-configuring:

Code: Select all

sudo dpkg-reconfigure solydkbo-siwapp


SolydXK needs you!
Development | Testing | Translations

User avatar
Tuna130
Posts: 47
Joined: 10 Aug 2013 05:40
Location: Spain

Re: SiWapp versus Frontaccounting

Postby Tuna130 » 15 Oct 2014 12:31

Got it. It is working again. Conclusion: something corrupted the MySql database and took down Siwapp.

I followed the advise by Schoelje, and came to the dpkg-reconfigure, and said yes to building a new database. It complained about an existing siwapp database. This needs removing first, through http://localhost/phpmyadmin . Earlier on in this thread Schoelje indicated how to do this. Then tried again, and Siwapp was back!

After checking that it was working again ( :D ), I logged out an went back to http://localhost/phpmyadmin . From there selected the siwapp database and clicked Import. From there the Saturday morning backup was good and put our company back in business, literally. When loading the Sunday morning backup Siwapp crashed, so the problem lies in that file.

I am happy that it works again. I lost a full day work of tedious invoicing and grew some grey hairs for three days, but I have learned a bit about the php admin tool. Why this could happen is a mystery to me, but as a precaution I shall log out of Siwapp after work. Also the automatic backups have proven to be important!

Thanks for your help!

-

User avatar
Arjen Balfoort
Site Admin
Posts: 8720
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: SiWapp versus Frontaccounting

Postby Arjen Balfoort » 15 Oct 2014 13:01

A corrupt backup...that explains a lot!
If it is really important you'll need to test a backup regularly (creating a new database with a different name or another MySql server) and keep those backups somewhere safe.


SolydXK needs you!
Development | Testing | Translations

User avatar
Tuna130
Posts: 47
Joined: 10 Aug 2013 05:40
Location: Spain

Re: SiWapp versus Frontaccounting

Postby Tuna130 » 18 Nov 2014 23:57

Err, no. The corrupted database was backed up correctly.
My victory lasted for three days, and then mysqld failed and I could not access phpMyAdmin anymore.
I tried to find a solution, and I think I found it, here we go.

What I think may have caused the problem: I use SolydX Home Edition and it seems Siwapp package was dropped from this repo. (Sorry if I missed announcements around this item.) Some dependency issue must have crept up, messing with MySQL.
So I use a repo based on 'testing' while the package lives in the business 'stable' repo. Right?

So for package solydkbo-siwapp I need to downgrade to stable. I am not an expert on this, but I added the before mentioned lines to my /etc/apt/sources.list and then tried apt-pinning to give preference to 'testing'. (As per https://wiki.debian.org/AptPreferences.)

/etc/apt/sources.list

Code: Select all

### Home Edition: (Testing)
deb http://ftp.nluug.nl/os/Linux/distr/solydxk/debian/production testing main contrib non-free
deb http://ftp.nluug.nl/os/Linux/distr/solydxk/debian/production/multimedia testing main non-free
deb http://ftp.nluug.nl/os/Linux/distr/solydxk/debian/security testing/updates main contrib non-free
deb http://ftp.nluug.nl/os/Linux/distr/solydxk/packages/production/ solydxk main upstream import
deb http://community.solydxk.com/production/ solydxk main
### Business edition: (Stable)
deb http://business.solydxk.com/production solydxk main upstream import
deb http://business-debian.solydxk.com/production solydxk main contrib non-free
deb http://business-debian.solydxk.com/security solydxk main contrib non-free
/etc/apt/preferences

Code: Select all

Package: *
Pin: release a=testing
Pin-priority: 900

Package: *
Pin: release a=solydxk
Pin-priority: 800
I hope this is correct procedure, and will not cause problems later on. Please let me know if this is wrong...

After 'apt-get update' I was able to reinstall solydkbo-siwapp, and get mysqld started. I could then access phpMyAdmin again, erase user siwapp and database siwapp. Then I could successfully run

Code: Select all

sudo dpkg-reconfigure solydkbo-siwapp
.

The next step, importing the backup database resulted in an error. Here the trick was to first erase the siwapp database (not user siwapp), then create an empty database named siwapp, and then import the backup. :)

User avatar
Zill
Posts: 1850
Joined: 13 Aug 2013 14:28
Location: Lincolnshire, UK

Re: SiWapp versus Frontaccounting

Postby Zill » 19 Nov 2014 11:18

Tuna130 wrote:...What I think may have caused the problem: I use SolydX Home Edition and it seems Siwapp package was dropped from this repo. (Sorry if I missed announcements around this item.) Some dependency issue must have crept up, messing with MySQL.
So I use a repo based on 'testing' while the package lives in the business 'stable' repo. Right?
This is really not a good idea! Mixing testing and stable repos in this way is a recipe for disaster.

I don't use Siwapp so cannot comment on this application directly but, I suggest, you should only use packages intended for your specific distro version. SolydXK HE is a semi-rolling release based on Debian Testing and has quarterly updates. SolydXK BE is a static release based on Debian Stable and therefore has very few updates. By mixing these repos you are getting incompatible packages installed that will lead to breakage.

My best advice is to decide if you want to run HE or BE and then stick to it and do not install any packages from another release unless you really know how to handle any resulting dependency problems. Unfortunately, your system may now be so confused that a full re-install is the best option.

Note that in a few months SolydXK HE and BE editions will merge to become the "new" SolydXK. This release will be based on the next Debian Stable, codenamed Jessie.

User avatar
Tuna130
Posts: 47
Joined: 10 Aug 2013 05:40
Location: Spain

Re: SiWapp versus Frontaccounting

Postby Tuna130 » 20 Nov 2014 14:01

Thanks Zill, I was afraid of something like that. I think at the time I installed Solydxk the BE was KDE only, and I preferred XFCE, and hence took the HE.

So if my current HE setup is the future BE setup, and I indeed want to change to BE, then I suppose I'll leave my system like it is. It works for now, and I don't want to break it. So I'll just not update/upgrade anything untill Jessie becomes stable and my system will be magically transformed to BE. :)

We need Siwapp, so my only other alternative would be to reinstall with BE. But that would be a real bummer, I came from Ubuntu to Solydxk to avoid those reinstalls...

User avatar
Arjen Balfoort
Site Admin
Posts: 8720
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: SiWapp versus Frontaccounting

Postby Arjen Balfoort » 20 Nov 2014 14:28

You can always download from the siwapp site.
The installation is pretty straightforward.

http://www.siwapp.org/


SolydXK needs you!
Development | Testing | Translations

User avatar
Zill
Posts: 1850
Joined: 13 Aug 2013 14:28
Location: Lincolnshire, UK

Re: SiWapp versus Frontaccounting

Postby Zill » 20 Nov 2014 14:47

Tuna130 wrote:...So if my current HE setup is the future BE setup, and I indeed want to change to BE, then I suppose I'll leave my system like it is. It works for now, and I don't want to break it. So I'll just not update/upgrade anything untill Jessie becomes stable and my system will be magically transformed to BE...
Unfortunately, I don't think it is quite that simple! Your current sources.list has both Testing and Stable repos in it, which means that every time you update/upgrade your system doesn't really know which core packages and dependencies to change. This means that your system is probably already broken and this situation will be compounded when the next SolydXK HE update pack is released.

I hate to say it but I really think that a full re-install is the easiest solution if you are to avoid problems. Otherwise you will need to change your sources.list to either Testing or Stable repos and then laboriously go through your system fixing any and all broken packages.

Of course, once your system is running properly on a single repo version, such as Stable, then there will be no future need to re-install. Just don't add any more repos to the default ones! ;-)

User avatar
grizzler
Posts: 1992
Joined: 04 Mar 2013 15:45
Location: The Hague, NL

Re: SiWapp versus Frontaccounting

Postby grizzler » 20 Nov 2014 15:11

If the pinning worked, I wouldn't expect anything that was also in HE/Testing to have been updated from BE/Stable (unless I still don't understand pinning correctly... which is by no means impossible). So I'm not convinced reinstalling would be necessary. Removing the BE items from sources.list, yes, that would be a good idea...
Frank

SolydX EE 64 - tracking Debian Testing

User avatar
Zill
Posts: 1850
Joined: 13 Aug 2013 14:28
Location: Lincolnshire, UK

Re: SiWapp versus Frontaccounting

Postby Zill » 20 Nov 2014 15:29

grizzler: I agree that pinning, done properly, could hold it all together. However, I have seen several "tales of woe" where pinning does not seem to do exactly what the user intended. I am a great believer in the old "KISS" adage (Keep it simple, stupid!) and I prefer to eliminate the cause of problems rather than fix them later, hence my advice for a clean re-install.

User avatar
Tuna130
Posts: 47
Joined: 10 Aug 2013 05:40
Location: Spain

Re: SiWapp versus Frontaccounting

Postby Tuna130 » 20 Nov 2014 22:43

Yes, this whole pinning business is scary. Great if it works, but great trouble if it doesn't.
I have now commented out the BE repos in the sources.list, just to be sure.
Now, I'll be careful when upgrading, if at all.

The system is still 99% 'testing', it only pulled in the Siwapp package from 'stable', thanks to pinning.
Just to be on the safe side, I want to hold any updates on Siwapp package and its dependencies.

To find dependencies I did:

Code: Select all

$ apt-cache depends solydkbo-siwapp
solydkbo-siwapp
 |Vereisten: debconf
  Vereisten: <debconf-2.0>
    cdebconf
    debconf
  Vereisten: dbconfig-common
  Voor-Vereisten: apache2
  Voor-Vereisten: mysql-server
  Voor-Vereisten: php5
  Voor-Vereisten: php5-mysql
  Voor-Vereisten: libapache2-mod-php5
  Voor-Vereisten: mysql-client
    mysql-client-5.5
  Voor-Vereisten: php5-xsl
And then to hold those packages:

Code: Select all

$ sudo apt-mark hold dbconfig-common apache2 mysql-server php5 php5-mysql libapache2-mod-php5 mysql-client php5-xsl
dbconfig-common set on hold.
apache2 set on hold.
mysql-server set on hold.
php5 set on hold.
php5-mysql set on hold.
libapache2-mod-php5 set on hold.
mysql-client set on hold.
php5-xsl set on hold.
Debconf better be left alone. MySQL-client was probably not necessary to hold.

Hope this works! I'll read the Siwapp website when I get the chance. Cheers!


Return to “SolydK Back Office”

Who is online

Users browsing this forum: No registered users and 1 guest