installation of gnuhealth Ubuntu 14.04 (2)

Hi there, again,

On the installation routine’s circumstances

If one’s mind comes on the installation of gnuhealth project. Is not it such that in each circumstance of today’s life one asks for the design behind it? How it was meant once when it was set into the world. What about circumstances? Hey, this project is really kind of politicon, is not it firstly to mention? They run the health hospital system of a whole state, Jamaika. WOW. <—This is the NGO I am member of…

The second thing that needs to be acknowledged, the development seems to be active and by a considerable small team. And therefore new bugs and changes that might make in the long consequence the installation routine – busy or/and broken.

Third thing: These development team is be seen tackling however with new kind of “better-handbook-only” documentation delivery strategy to the end costumers.

So that is the thread to follow: Having_ a closer look to the handbook a wikipedia hosted wikibook then.

Lets recap what I as a defined as such: Testuser, experienced on my way through the installation process. My first impression is: supoptimal.

First: One ever asks oneself: Do they not want to let know how a anybody could install there software intriguedly? That keeps us away half from lust getting through this installation process. Why had not they talked about the warning that could be enduring weeks?

Second: On Wikibooks where the contents is to study from kind of html-generation way, noway in a form pdf-book, so there is yes bread crumb but there is no centralized contents index on the top of the wikibook and I dislike that- I say this just for the difference in the handling which stakes out. To this second point is to add:  Ah, if we have a straight look on the centralized contents index on the top of the wikibook. We found the point sabotage, – no joke trouble shooting. – It is empty. They say something of one could write one oneself an article over the trouble shooting. In the end all bores down to truth that we all should weapon ourselves with logging and tool-analyzing tools that all we could bore down to whichever assembler level of world history. Right? So what? Where are these tool for this way on what prepared, would one indeed ask constructively?

Fourth: This comes effectively so:

One is to ask: If not a more bread crump wise installation could be designable?

Lets open the wikibook Gnuhealth page on installation then:

On the red thread of the gnuhealth installation process

The point in this current gnuhealth installation routine is that it is noway bread crumb navigation, but maybe the opposite of it. The handbook reader is not be able to prepare the necessary for this from the beginning on:

-there is first a data base company hack to fulfill. Which has two steps. The second step waits as the most difficult point in the installation process:

https://en.wikibooks.org/wiki/GNU_Health/Installation#Creating_the_GNU_Health_database.

Here is where user graphically-only is urged and where with considerable time risk he can proof most early, if all hours enduring work before were successful. This is what I mean that is neither expectable nor bread crumb.

Then -for the handbooks defense one could could point the newbie from the beginning on to this passage out of this chapter:

Check in the server log (or console) if any error occurs. If so, try to fix the problem (ie. any Python module missing or some unmet dependencies), drop the database just created and repeat the procedure.

And keep the compile script output on stdin and stdout logged next time one might add. Update: Yes and there will be opened a list of useful tools in this situation.

And this is the solution in short words to be prepared on this bottle neck: There are in 8 eight textbox datas to be entered by a user. This is more shining a test for IQ or aberridical behavior . So the best bet is to make a table on a paper with a column 8 interface variables with their textbox names on. Then read carefully which whole information you get out the handbook. Developing a best bet 8 column variation? Yes, this is what it is actually about.

You have to denominate a database and it’s database-user and it’s password. Please build a rational sentence of database, database user and database user password might one ask? Hm. It comes grosser. Yes and then stick the word “PostgreSQL” in it with out stumbling? He?

OK further on there is a server more to who we connect. Tryton server, User, password and two options on tcp/ip on a so call rpc-machine-never-heard-of. The latter seems ok.(nmap localhost) So then we have a user and a password. And here the thriller begins. After some discriminating jury “admin, admin” would be the choice but: No. In the end functioned by trial and error a considerably long time: that admin indeed is the indicated and existing user in Tryton Server, but his password were not admin. By heuristic googling I found some posts of same error message. And I got to the handbook page of resetting the password.  – I had to reset my bash console meanwhile and unsuccessfully. Hm –  So you got two passwords and completed all column.

Here should open up the graphical application of gnuhealth.

on second run: installation of gnuhealth

here are some command lines I found worth to be mentioned. Have fun with it:

apt-get install libxml2-dev libxslt1-dev
apt-get install python-cracklib

# I found that I needed to install them, after two times unsuccessfully had run the compile script. But if one compares here https://en.wikibooks.org/wiki/GNU_Health/Operating_System-Specific_Notes#Install_dependencies_4, they already should had been in..

rm -rf ../gnuhealth
rm -rf /tmp/gnuhealth_installer # for cleaning up in the mean while.

~/gnuhealth-2.8.1 $ ./gnuhealth_install.sh > ./mylog.txt 2>&1 &
#[1] 22678
#gnuhealth@:~/gnuhealth-2.8.1 $
#[1]+ Exit 1 ./gnuhealth_install.sh > ./mylog.txt 2>&1

ps aux|grep trytond
#gnuheal+ 16213 0.0 0.4 364436 15376 pts/3 Sl Mai15 0:07 python ./trytond
#gnuheal+ 21954 0.0 0.0 18932 968 pts/3 S+ 13:55 0:00 grep –color=auto trytond
kill 9 16213

#107 in another Console: tail -f gnuhealth-2.8.1/mylog.txt

./tryton -v –log-level=DEBUG

#INFO:tryton.rpc:common.db.db_exist(None, None, (‘gnuhealth’,))
#DEBUG:tryton.rpc:False
#INFO:tryton.rpc:common.db.create(None, None, (‘gnuhealth’, ‘6678werhu8’, ‘en_US’, ‘444nteh4’)

./trytond –logconf /home/gnuhealth/gnuhealth/tryton/server/config/gnuhealth_log.conf -v

# Error Message:

#Access denied!
#Sorry, wrong password for the Tryton server. Please try again.

printf ’44tth4\n44ttnh4’|su – postgres -c “createuser –createdb –no-createrole –no-superuser -P gnuhealth”

find /home/gnuhealth/ -name “serverpass*”

printf ‘467677h4\n467677h4’|python serverpass.py # have not checked the printf though. I think finding this ridiculous is serious.

psql -l

su postgres -c ” dropuser gnuhealth”
su postgres -c ” dropdb gnuhealth”
su – postgres -c “psql -P format=unaligned -c ‘\l'”|grep gnuhealth;su – postgres -c “psql -P format=unaligned -c ‘\du'”|grep gnuhealth

#http://www.binarytides.com/install-postgresql-phppgadmin-pgadmin-ubuntu/ for those who want to to inspect their data base at least once graphically.

Screenshots of the chase:

installinggnuhealth_error_hb4_postgrestrusts

installinggnuhealth_error_hb7_look_installationscript2installinggnuhealth_error_hb5_postgreststoppdemon

installinggnuhealth_error_hb6_look_installationscript

installinggnuhealth_error_hb7_look_installationscript4

installinggnuhealth_error_wiped_outjpg4putt

installinggnuhealth_error_wiped_outjpg2

I see then several, do not know how much time it needs. This form is the user having to wait why?

installinggnuhealth_error_hb7_look_installationscript6

installinggnuhealth_error_hb7_look_installationscript10

incredible

nmap localhost
root@:~# cat 1-tog|grep 8000 |wc
108    2580   18924
root@:~# cat 1-tog|grep 5432 |wc
  1429   34227  257520
root@:~# tcpdump -nvvvi lo >1-tog&

root@:~# cat 1-tog|grep 5432 |grep incor|wc
1418   34062  256313
root@:~# cat 1-tog|grep 5432 |grep -v incor
127.0.0.1.5432 > 127.0.0.1.41868: Flags [R], cksum 0xf532 (correct), seq 3782025849, win 0, length 0
127.0.0.1.5432 > 127.0.0.1.41870: Flags [R], cksum 0x9e84 (correct), seq 1587608562, win 0, length 0
127.0.0.1.5432 > 127.0.0.1.41872: Flags [R], cksum 0xe6a1 (correct), seq 3386787989, win 0, length 0
127.0.0.1.5432 > 127.0.0.1.41874: Flags [P.], cksum 0xfe82 (correct), seq 6381:6471, ack 4457, win 429, options [nop,nop,TS val 123825025 ecr 123825025], length 90
127.0.0.1.5432 > 127.0.0.1.41874: Flags [R], cksum 0xf331 (correct), seq 3349364286, win 0, length 0
12:26:25.454323 IP (tos 0x0, ttl 64, id 31270, offset 0, flags [DF], proto TCP (6), length 52)
127.0.0.1.5432 > 127.0.0.1.41877: Flags [R], cksum 0x87f2 (correct), seq 925907438, win 0, length 0
127.0.0.1.41878 > 127.0.0.1.5432: Flags [R], cksum 0x35c9 (correct), seq 3254255950, win 0, length 0
127.0.0.1.5432 > 127.0.0.1.41880: Flags [R], cksum 0x9239 (correct), seq 4100616809, win 0, length 0
127.0.0.1.41881 > 127.0.0.1.5432: Flags [R], cksum 0xf740 (correct), seq 2401465000, win 0, length 0
127.0.0.1.5432 > 127.0.0.1.41882: Flags [R], cksum 0xe58e (correct), seq 3049479609, win 0, length 0
root@:~# cat 1-tog|grep 5432 |grep -v incor

I lost some what the patience and wanted to know what they were talking about. Like Mister Tottle, and out of curiosity because I am new to three Tier. Ask tcpdump: here I liked that http://albanianwizard.org/tcpdump-how-to-the-linux-troubleshooter.albanianwizard

All that noise on the cable about some unmet checksums…

Ok, I have been grown minister of the GNU-Hostital now? Anyway I do not find it good what you do with all that poor Jamaican patients there.

That will be the structure for my first tramp company. So what: this was the installation of GNU Health, it took three days. Thank you for reading!

Vista install in 2 minutes, here we go

For comparison how a service design can be concieved as well: https://www.youtube.com/watch?v=FVbf9tOGwno

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s