View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004758 | Taler | obsolete component | public | 2016-11-03 13:07 | 2016-11-20 03:26 |
Reporter | Marcello Stanisci | Assigned To | Marcello Stanisci | ||
Priority | high | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Product Version | git (master) | ||||
Target Version | 0.2 | Fixed in Version | 0.2 | ||
Summary | 0004758: unix socket not created by python script | ||||
Description | When the bank is launched by 'taler-bank-manage serve-uwsgi', the expected unix domain sockets in /tmp are not created. If instead the bank is launched with: uwsgi --emperor <PFX>/share/taler-bank/vassals-unix/ then the sockets are correctly created. | ||||
Tags | No tags attached. | ||||
|
Adding the Python guru :-) |
|
Why do we even have sockets in the global '/tmp'? I don't understand the problem well enough to give any advice. Is there a reason we need to use uwsgi's emperor/vassal mechanism? Can't we just have two uwsgi services, one for the bank's admin interface and one for the frontent, both run separately by gnunet-arm? |
|
We use the emperor thing because is the uwsgi way of running multi app/instances services, and we launch both apps with one command. It is also handier to launch the bank manually for quickly looking at the output. Basically, any vassal gets configured in a .ini file, and in those files you indicate where on the filesystem you want your sockets created. Sockets in /tmp are just a default value we have for vassals (as we don't want to save on git tripwire's specific paths like ~/sockets/). It can be changed in <PFX>/share/taler-bank/vassals-unix/*.ini. The good side of your solution is that we don't move away part of the configuration from ~/.config/taler.conf. I'm not strictly against. |
|
Hmm, I wouldn't be completely opposed to using uwsgi's vassals/emperor, but it seems like it's more of a pain than a gain. So unless it simplifies things a lot, we should just have two separate services! |
|
Fixed in 174dab7. Actually preferred changing the implementation to your suggestion instead of indagating why the Emperor does not create sockets. (test) config file in deployment also updated. |
Date Modified | Username | Field | Change |
---|---|---|---|
2016-11-03 13:07 | Marcello Stanisci | New Issue | |
2016-11-03 13:07 | Marcello Stanisci | Status | new => assigned |
2016-11-03 13:07 | Marcello Stanisci | Assigned To | => Marcello Stanisci |
2016-11-03 13:37 | Marcello Stanisci | Additional Information Updated | |
2016-11-03 13:38 | Marcello Stanisci | Priority | normal => high |
2016-11-03 14:45 | Marcello Stanisci | Note Added: 0011412 | |
2016-11-03 16:23 | Florian Dold | Note Added: 0011413 | |
2016-11-03 17:30 | Marcello Stanisci | Note Added: 0011414 | |
2016-11-03 19:35 | Florian Dold | Note Added: 0011417 | |
2016-11-04 13:47 | Marcello Stanisci | Note Added: 0011425 | |
2016-11-04 13:47 | Marcello Stanisci | Status | assigned => resolved |
2016-11-04 13:47 | Marcello Stanisci | Resolution | open => fixed |
2016-11-15 15:41 | root | Product Version | => git (master) |
2016-11-15 15:41 | root | Fixed in Version | => 0.2 |
2016-11-15 15:41 | root | Target Version | => 0.2 |
2016-11-20 03:26 | Christian Grothoff | Status | resolved => closed |
2022-08-23 20:26 | Christian Grothoff | Category | bank (demonstrator) => py bank (demonstrator, obsolete) |
2023-12-03 01:23 | Christian Grothoff | Category | py bank (demonstrator, obsolete) => obsolete componet |
2023-12-11 20:08 | Florian Dold | Category | obsolete componet => obsolete component |