by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Steffan Cline
    @SteffanCline
    it’s a security feature in CentOS 7 +
    RHEL7+
    each app has a private tmp unless you say to make it public. There are some updates that will revert this from time to time.
    Shelane French
    @shelane
    systemd was on the patch list from Wednesday night. I'm checking now...
    Here it is: PrivateTmp=true
    Steffan Cline
    @SteffanCline
    Bingo!
    Shelane French
    @shelane
    That was it!!! You d'man!
    Steffan Cline
    @SteffanCline
    :D
    Shelane French
    @shelane
    Now I'm looking like the hero at work, but you're my hero @SteffanCline!
    Steffan Cline
    @SteffanCline
    👍🏼
    Johan Sölve
    @johansolve
    wow
    Steffan Cline
    @SteffanCline
    wow, what?
    I posted this to LKC a long time ago
    Johan Sölve
    @johansolve
    The solution. Thanks! In case I run into it too.
    Steffan Cline
    @SteffanCline
    Steffan Cline
    @SteffanCline
    Sent. I emailed it to you and Shelane so you can save it
    Johan Sölve
    @johansolve
    yeah, but I meant that I can find the solution in lkc if needed :)
    thanks!
    Steffan Cline
    @SteffanCline
    I’ve seen that error a few times. I think that with all the updates to CentOS 7, it’s only been broken once.
    That was 2015. Wow… I recall Jason hit it years ago. Unfortunately he’d already created a custom install of Apache to get around it by then.
    Shelane French
    @shelane
    So I don't know if Lasso just handles file uploads differently or what, but I checked my other server that runs php sites and they upload fine with it set to true.
    Steffan Cline
    @SteffanCline
    I think PHP does it’s whole file upload differently. I don’t recall seeing anything in the Apache APIs showing a method of getting the private tmp. Maybe that’s changed. I haven’t gone back to look.
    Johan Sölve
    @johansolve

    I use Steffan’s include_url using os_process to call curl directly. Have some problems I don’t understand. Headers arent’ sent.
    For example resulting command /usr/bin/curl -L --tlsv1.2 -d '{"payment": "..."}' -X POST -i -H 'Authorization: Bearer xxx' -H 'Content-Type: application/json' -H 'Accept: application/json’ works fine on command line but through os_process the headers aren’t sent, just plain content-type: application/x-www-form-urlencoded.

    If I modify the os_process call so curl is called through /bin/sh then it works.
    /bin/sh curl -L --tlsv1.2 -d '{"payment": "..."}' -X POST -i -H 'Authorization: Bearer xxx' -H 'Content-Type: application/json' -H 'Accept: application/json’

    What do I miss?

    Steffan Cline
    @SteffanCline
    I wonder if it’s an encoding issue or charset issue. I used that a bunch of times for the same purpose and it was fine.
    I wonder if you out the @ before the literal if it would ensure there was no encoding.
    Are you positive my tag is being called?
    Have you used ps at the command line to see what Lasso did? If you execute ps auxww right after Lasso tried it, you might be able to find that in the list.
    Johan Sölve
    @johansolve
    I know the right include_url is called, I have modified it slightly and added debug code in it so I know it gets called.
    Johan Sölve
    @johansolve
    I finally got it working by rewriting include_url to use /bin/bash -c
    local('myProcess' = os_process('/bin/bash', array('-c', 'curl ' + #flags->join(' ')) ));
    Johan Sölve
    @johansolve
    I can’t figure out how, but I was inspired by how the shell custom tag used os_process and gave it a try to do the same. Not sure who wrote that, maybe Jason Huck?
    ANyway, now works on both local Mac and CentOS
    Steffan Cline
    @SteffanCline
    Jason wrote that.
    DustyLoon
    @DustyLoon

    So I can't seem to figure out how to get LP8.6 running on a modern Mac, so I'm looking at running Mac OS X 10.8 (Mountain Lion), which seems to have been the current OS when LP8.6 was released in a VM so that LP behaves. Am I doing this the hard way?

    Chrome requiring TLS 1.2 really is punishing me for holding out on my 10.6 server running LP8.5 this long. I knew I needed to upgrade, but every time I've tried I've failed to get Lasso running. I just spent two days trying to get centos (5/6/7) and lasso 8.6 to work together and failed.

    Maxwell
    @maxwellk2
    It’s been a while but here are the notes I have on getting Lasso8.6, Lasso9.3, and FileMaker Server all running under 10.15 Mojave. I started on a Paralles VM to confirm then migrated to a Mac mini at MacStadium.com. The rest of the thread has some additonal info. http://lasso.2283332.n4.nabble.com/Lasso-8-6-and-OSX-Mojave-tp4646512p4646684.html
    Oops, I mean “10.14 Mojave"
    DustyLoon
    @DustyLoon
    Thank you! I'll start playing with this in a VM first right away. Then I gotta find a cheap Mac mini that still runs Mojave. Thanks again for sharing your notes, it's a huge help!
    Maxwell
    @maxwellk2
    Glad that can be of some help. The Mac mini 6,1 "Late 2012" with the 2.6 Ghz processor and newer SSDs is still a solid server.
    DustyLoon
    @DustyLoon
    You wouldn't have a source on old minis perchance? This is for a non-profit, but I'll kick in a few bucks if I have to.
    DustyLoon
    @DustyLoon
    I mean that to say, if the non-profit can't afford new hardware, then I guess my taxes are going to show yet another charitable donation.
    Maxwell
    @maxwellk2
    DustyLoon
    @DustyLoon
    Thanks again!
    DustyLoon
    @DustyLoon

    Well it's been a long day of striking out. The reason for the need to upgrade is Chrome depreciating TLS anything older than 1.2. I need to find a Mac server version that handles TLS 1.2 while can also run LP8.6. I fired up the VM for testing. The installer won't run at all on 10.15 (being 32bit), using the instructions from Maxwell I was hopeful for 10.14 server, but the LP installer fails. Tried 10.13 and the installer fails.

    Ugh.

    DustyLoon
    @DustyLoon
    Fails on 10.12 as well.
    Maxwell
    @maxwellk2
    Did you disable SIP? It’s been a while since I got this all working, but I know it can be done….
    Screen Shot 2020-07-30 at 11.04.27 AM.png
    DustyLoon
    @DustyLoon
    Would that affect the OS running in a VM?
    I have an old iMac that runs 10.13, I'll give that a go. Didn't think SIP would be a factor in a VM, but I'm not well versed in VMs either.
    DustyLoon
    @DustyLoon
    You were right once again, it was a SIP issue, even though I was working in a VM.
    DustyLoon
    @DustyLoon
    @maxwellk2 Man, I owe you dinner. Worked on an old iMac after I disabled SIP. Gonna do a test run on the main machine with a VM, then it's off to buy a Mac mini that runs 10.14.
    DustyLoon
    @DustyLoon
    Yuppers, works in the VM with 10.14 (didn't occur to me command-R works in a VM! This is why you should leave this work to the professionals). Thanks again!