Stan, I should have mentioned. In the rel file you will see a bunch of tuples of <app>, <vsn>. The versions in the rel file there are probably wrong for 5.9. It should be pretty easy to update it and rerun the make_script. All the apps specified there and the versions must exist.
On Wed, Mar 14, 2012 at 5:57 PM, Stan McQueen <[email protected]> wrote: > Thanks, Eric. It works up to a point. I updated sinan.rel with the R15 > versions of all the dependencies and ran make_script to produce > sinan.script and sinan.boot. When I attempt to run "sinan dist" the > release step fails with the error message "build problem > sin_task_release:209 [release_script_generation_error] *WARNING* : > Missing application sasl. Can not upgrade with this release". > Interestingly, the .boot, .script, and .rel files are created, but the > error means that sinan doesn't proceed to the dist task to create a > tarball that faxien can publish. > > Running "sinan shell" and starting appmon shows that sasl is running, > so I don't know what the problem is. Perhaps there is still a > configuration issue. Just in case you can use it, I've attached my > sinan.rel file. > > I certainly appreciate all your efforts. I know that this is a > distraction from your normal workload and I'm very sorry for that. I > was able to deploy our server apps by hand to my development server > and verify that R15 does fix the problem with public_key, so it's > worthwhile for me to continue the effort to more to the new version of > Erlang. No worries and Let me know if there is anything I can do to help. > Stan > > On Wed, Mar 14, 2012 at 3:42 PM, Eric Merritt <[email protected]> wrote: >> Stan, >> >> Because of the nature of erlangs code loader you cant actually use >> sinan to build sinan, at least not without a bunch of head twisting, >> which is what the makefile does. >> >> Attached is a version of sinan-1.0.1 compiled on R15. You can drop it >> in though you will need to change the erts to 5.9. >> >> You should also probably change the rel file and run make_script >> again. (I actually suspect this is your problem on starting in 5.9) >> >> I realize this is non-optimal, but I am really not set up to build >> 1.0.1 anymore. If we continue to run into problems I may just have to >> though. >> >> On Wed, Mar 14, 2012 at 1:17 PM, Stan McQueen <[email protected]> wrote: >>> That would be great, thanks. I've tried changing ERTS_VSN in the sinan >>> script to 5.9. When I do that, I get errors because prim_inet:open/2 >>> is undefined. Using ERTS_VSN of 5.8.4 or 5.8.5 causes errors in >>> epp:parse_file. I've also tried using the new sinan to build >>> sinan-1.0.1 under R15, but get lots of errors trying that. >>> >>> Stan >>> >>> On Wed, Mar 14, 2012 at 11:08 AM, Eric Merritt <[email protected]> >>> wrote: >>>> On Wed, Mar 14, 2012 at 11:45 AM, Stan McQueen <[email protected]> >>>> wrote: >>>>> Eric, >>>>> >>>>> Thanks for your reply (and thanks again to you, Martin, and Richard >>>>> for writing "Erlang and OTP in Action." I have the original eBook >>>>> version as well as the published one. The original is what got me >>>>> started on the Erlware tools). >>>>> >>>>> Unfortunately, I haven't been able to get sinan 1.x to run under >>>>> Erlang R15; that's what initiated this whole process. (I had to >>>>> upgrade to R15 to fix a bug in the public_key module, although I could >>>>> also attempt a patch). So at this point I am somewhat committed to >>>>> coming up with a deployment solution for the following version of our >>>>> server. We're preparing to deploy the second version (1.1) of our >>>>> server, but that one is still on R14B04, so our existing Erlware tools >>>>> work fine. The following version, version 1.2, is the one that >>>>> requires the public_key fix (apparently Macintosh self-signed SSL >>>>> certs aren't handled correctly by the R14B04 public_key module). >>>> >>>> Stan, I may be able to get a coupy of your version of sinan (the last >>>> in the 1.0 series) and get that building under R15. It sounds like its >>>> pretty important to your business. I wont commit to supporting it >>>> indefinitely but I can probably help you out of this hole. >>>> >>>>> >>>>> For some background, we have two eleven-machine clusters (not counting >>>>> the firewall and load balancers), one for production and one for test. >>>>> Of the eleven machines, two are Erlang servers (the others are tomcat >>>>> servers, MongoDB servers, RabbitMQ servers, etc), each with a >>>>> complement of several major Erlang components made up of several >>>>> applications each. Deploying a new version involves pulling down two >>>>> major packages from portius and installing them via faxien. One >>>>> package consists of four applications and the other has approximately >>>>> 20 applications. So the deployment and installation is somewhat >>>>> complex. To date, we have used the Erlware tools quite successfully >>>>> and I am reluctant to move in another direction unless forced. >>>>> >>>>> Sinan 2.x produces a directory structure that doesn't seem compatible >>>>> with faxien. Under sinan 1.x, the structure was >>>>> "_build/development/apps" while under sinan 2.x, it is >>>>> "_build/<NAME>/lib". I tried to point "faxien publish" at the >>>>> subdirectories under "lib", but got a function_clause error from >>>>> ewr_repo_paths, possibly caused by a mismatch between the erts version >>>>> and the compiler version. I'll continue to look at this. >>>> >>>> Sinan 2.0 changed to be more directly compatible with an OTP Release >>>> and more or less disregarded faxien since it was deprecated at that >>>> point. >>>> >>>>> >>>>> The tar file produced by "sinan dist" appears to contain everything I >>>>> need to deploy, but I'm not sure how to do it. I'm thinking of storing >>>>> it in MongoDB and creating an escript to retrieve it, unpack it, and >>>>> distribute it to the Erlang lib and release directories to simulate >>>>> what the current faxien/portius combination does. >>>> >>>> Tristan does something very similar to this and has lots of experience >>>> managing deployments like this. I will has him to chime in with >>>> advice. >>>> >>>>> >>>>> I would love to use the platform tools; unfortunately, although we >>>>> develop on Ubuntu and could use the Debian packages there, the >>>>> production servers are Gentoo (our IT department loves it for some >>>>> reason). >>>> >>>> ah, understandable. Well lets get you out of this hole and then we can >>>> figure out a long term solution. >>>> >>>>> >>>>> Stan >>>>> >>>>> On Wed, Mar 14, 2012 at 9:06 AM, Eric Merritt <[email protected]> >>>>> wrote: >>>>>> On Tue, Mar 13, 2012 at 3:58 PM, Stan McQueen <[email protected]> >>>>>> wrote: >>>>>>> That works; thanks very much. Now my problem is as follows: >>>>>>> >>>>>>> We're currently building with sinan, publishing to a portius repo with >>>>>>> faxien, and finally using faxien to install new releases on our test >>>>>>> and production servers. The new sinan doesn't seem to produce a >>>>>>> configuration that faxien understands. Previously, i could build a >>>>>>> release that contained a number of sub-projects, then "faxien publish" >>>>>>> would publish the appropriate combination of libs and releases to >>>>>>> portius. This process has been working very well for the 1.0 release >>>>>>> of our new servers. >>>>>>> >>>>>>> Is there an erlware replacement for this build-publish-deploy process? >>>>>> >>>>>> At the moment, no unfortunately. We are talking about a new and very >>>>>> interesting replacement for faxien/sinan. I suspect strongly that that >>>>>> will actually happen in the next few months. But it doesn't exist yet. >>>>>> There is a further misfortune that it doesn't exist currently in the >>>>>> larger erlang community either. >>>>>> >>>>>> There are three routes I think for you though none super wonderful >>>>>> >>>>>> 1) Continue to use faxien/sinan 1.0.0 series >>>>>> 2) Migrate to native packages for your platform >>>>>> 3) Wait for the new replacement >>>>>> >>>>>> I think 1 is probably not viable in the long term, as that >>>>>> faxien/sinan series bitrots. >>>>>> >>>>>> 2 actually works well though there is a lot of upfront work. If you go >>>>>> this route all of the usual build and deployment tools work. The >>>>>> downside is you have to learn packages and setup a native repo etc. >>>>>> However, this is the approach I took for the startup i am building. >>>>>> >>>>>> 3 would work as well, there is always a danger in waiting for >>>>>> something that doesn't exist but I am becoming more and more confident >>>>>> that we will build it. In this case you could continue down your >>>>>> present path with faxien/sinan until the replacement happens. >>>>>> >>>>>> There is an implicit 4th option that is rolling your own. I recommend >>>>>> against this. If you want to go that route its probably better to >>>>>> participate in 3 with us. >>>>>> >>>>>> If you want to go the second route and are using debian I can help you >>>>>> there. I have a lot of recent experiance packaging OTP Apps for >>>>>> debian. >>>>>> >>>>>> (not what you may have wanted to hear I know) >>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "erlware-dev" group. >>>>>> To post to this group, send email to [email protected]. >>>>>> To unsubscribe from this group, send email to >>>>>> [email protected]. >>>>>> For more options, visit this group at >>>>>> http://groups.google.com/group/erlware-dev?hl=en. >>>>>> >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google Groups >>>>> "erlware-dev" group. >>>>> To post to this group, send email to [email protected]. >>>>> To unsubscribe from this group, send email to >>>>> [email protected]. >>>>> For more options, visit this group at >>>>> http://groups.google.com/group/erlware-dev?hl=en. >>>>> >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "erlware-dev" group. >>>> To post to this group, send email to [email protected]. >>>> To unsubscribe from this group, send email to >>>> [email protected]. >>>> For more options, visit this group at >>>> http://groups.google.com/group/erlware-dev?hl=en. >>>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "erlware-dev" group. >>> To post to this group, send email to [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]. >>> For more options, visit this group at >>> http://groups.google.com/group/erlware-dev?hl=en. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "erlware-dev" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/erlware-dev?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "erlware-dev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/erlware-dev?hl=en. > -- You received this message because you are subscribed to the Google Groups "erlware-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/erlware-dev?hl=en.
