OK, I hacked it together apt-installing some shared libs.
With the patch applied I get:

k logs test-memcached-0
failed to open file for mmap: No such file or directory

Which is a bit strange - should not the file be created dynamically if it 
does not exist?

fredag 6. desember 2019 23.51.38 UTC+1 skrev Dormando følgende:
>
> It's going to use some caps (opening files, mmap'ing them, shared memory, 
> etc). I don't know what maps to which specific thing. 
>
> That error looks like an omission on my part.. 
>
>     mmap_fd = open(file, O_RDWR|O_CREAT, S_IRWXU); 
>     if (ftruncate(mmap_fd, limit) != 0) { 
>         perror("ftruncate failed"); 
>         abort(); 
>     } 
>
> missing the error check after open. 
>
> Try adding a: 
>
> if (mmap_fd == -1) { 
>   perror("failed to open file for mmap"); 
>   abort(); 
> } 
>
> between the open and if (ftruncate) lines, which will give you the real 
> error. I'll get that fixed upstream. 
>
> On Fri, 6 Dec 2019, David Karlsen wrote: 
>
> > Does memcached use any of these capabilities:
> https://unofficial-kubernetes.readthedocs.io/en/latest/concepts/policy/container-capabilities/
>  ? 
>
> > 
> > 
> > fre. 6. des. 2019 kl. 16:39 skrev David Karlsen <[email protected] 
> <javascript:>>: 
> >       So far I am stuck on: 
> > k logs test-memcached-0  
> > ftruncate failed: Bad file descriptor 
> > 
> > 
> >   - memcached 
> >     - -m 768m 
> >     - -I 1m 
> >     - -v 
> >     - -e /cache-state/memory_file 
> > 
> > -vvv does not reveal anything interesting. 
> > What could be the cause of this? 
> > 
> > lørdag 30. november 2019 18.03.23 UTC+1 skrev David Karlsen følgende: 
> >       Reading https://github.com/memcached/memcached/wiki/WarmRestart it 
> is a bit unclear to me if the mount *has* to be tmpfs backed, or it can be 
> a normal 
> >       fileystem like xfs. 
> >       We are looking into running memcached through 
> Kubernetes/containers - and as a tmpfs volume would be wiped on 
> pod-recreation 
> > 
> > -- 
> > 
> > --- 
> > You received this message because you are subscribed to the Google 
> Groups "memcached" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to [email protected] <javascript:>. 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/memcached/f39374e2-d603-43e6-928a-a9a0fc9e93ed%40googlegroups.com.
>  
>
> > 
> > 
> > 
> > -- 
> > -- 
> > David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen 
> > 
> > -- 
> > 
> > --- 
> > You received this message because you are subscribed to the Google 
> Groups "memcached" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to [email protected] <javascript:>. 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/memcached/CAGO7Ob1d002j0ve-aN6hBGncZWF7jR9ygpaz7B54wbQUGDA%2Beg%40mail.gmail.com.
>  
>
> > 
> >

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"memcached" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/memcached/8defad58-9248-466d-8e4a-14f9e4afd9af%40googlegroups.com.

Reply via email to