[17013] in athena10
Re: Postfix FQDN requested during installation
daemon@ATHENA.MIT.EDU (Aaron M. Ucko)
Sun Dec 1 14:18:23 2019
From: amu@alum.mit.edu (Aaron M. Ucko)
To: Anthony Grebe <agrebe@mit.edu>
CC: debathena <debathena@mit.edu>
Date: Sun, 01 Dec 2019 14:17:36 -0500
In-Reply-To: <f67c58f6-7306-ca71-668b-95aba3d9186f@mit.edu> (Anthony Grebe's
message of "Sun, 1 Dec 2019 08:56:44 -0500")
Message-ID: <udl5ziz7t4f.fsf@mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Oops, please try
initctl --system status zhm
or (if you still get "command not found)
/sbin/initctl --system status zhm
NB: Most likely, exactly one of those two variants will work.
Anyway, no need to apologize, and thanks for keeping the list copied.
-- Aaron
Anthony Grebe <agrebe@mit.edu> writes:
> Dear Aaron,
>
> Thank you for explaining this, and I apologize that it's taken me so
> long for me to respond.
>
> When I run "systemctl status zhm.service," I get the response
> "systemctl: command not found." It's not super important to fix this,
> so don't worry about trying to debug if this is a complicated problem,
> although if this is something straightforward I can try to implement
> it.
>
> Thank you,
> Anthony
>
> On 11/7/19 3:40 PM, Aaron M. Ucko wrote:
>> Thanks for clarifying!
>>
>> The difference between kinit and renew is that kinit is a standard
>> Kerberos utility that only obtains raw Kerberos credentials, whereas
>> renew is an Athena-specific alias that additionally authenticates to AFS
>> (via the Athena-specific fsid -a, though standard aklog will typically
>> also do) and tries to refresh your Zephyr service tickets.
>>
>> Speaking of Zephyr, what does "systemctl status zhm.service" report?
>>
>> -- Aaron
>>
>> Anthony Valenti Grebe <agrebe@mit.edu> writes:
>>
>>> Dear Ben,
>>>
>>> Thank you for your detailed response, and Im sorry that it took me so long to respond on my end.
>>>
>>> Ive tried answering both yes and no to the debathena-msmtp-mta prompt (on different install attempts), and it seems like Ive run into either prompts or
>>> installation problems either way. But if this step isnt necessary for accessing AFS, then I guess I will just leave the FQDN as localhost.mit.edu and not
>>> worry about this part.
>>>
>>> Ive tried to install debathena-standard from the installer script (that I got from debathena.mit.edu/install-debathena.sh) on both my laptop (running Ubuntu
>>> 14) and my Chromebook (running Ubuntu 16 on top of Chrome OS; Im not exactly sure how this works other than that Ubuntu lives inside a chroot). In the past,
>>> I hadnt been able to access AFS on my laptop, but for some reason it seemed to work today. (I think that Ive tried to run kinit before and still been
>>> unable to access AFS; today I tried renew instead, so maybe that is the difference?) Given that it now seems to be working on my laptop, I would believe that
>>> the Chromebook is having problems just because of conflicts between Ubuntu and Chrome OS.
>>>
>>> I cant seem to get Zephyr to work on either machine (it just says Hostmaster not responding while initializing Zephyr). This seems less important than AFS
>>> access, though, given that Zephyr doesnt seem to be in as widespread use as in the past.
>>>
>>> The one question I have left: Is there a difference between kinit and renew, and what is the point of each? I would have naively thought that I would use
>>> kinit to access AFS and only use renew if I had left my computer on for a long time, but empirically it seems like renew gives me access to AFS and kinit does
>>> nothing discernible.
>>>
>>> Thank you,
>>> Anthony
>>>
>>> On Oct 28, 2019, at 12:44 AM, Benjamin Kaduk <kaduk@mit.edu> wrote:
>>>
>>> Hi Anthony,
>>>
>>> There's a few points to cover here, so let me take them separately:
>>>
>>> This FQDN you're being asked for is part of the Postfix configuration, a
>>> mail transfer agent; it's unlikely to affect your ability to use AFS and/or
>>> zephyr. (Incidentally, my recollection is that most debathena systems
>>> ended up with exim, not postfix, but I could be misremembering. I believe
>>> there's also a question in the installer about debathena-msmtp-mta, for
>>> which a "yes" answer would probably avoid the postfix question.)
>>>
>>> The "correct" FQDN value to use depends on where your machine is located
>>> and who is providing the network for it. For example, machines in the
>>> W20-575 athena cluster had hostnames like w20-575-3.mit.edu because IS&T
>>> assigned them to be that way.
>>>
>>> Could you say a bit more about what procedure you're using to run the
>>> installation? In particular, what "metapackage" (like debathena-login or
>>> debathena-login-graphical) do you pick, and are you getting the installer
>>> script itself from https://debathena.mit.edu/install-debathena.sh ?
>>>
>>> Thanks,
>>>
>>> Ben
>>>
>>> On Sat, Oct 26, 2019 at 12:02:24PM -0400, Anthony Valenti Grebe wrote:
>>>
>>> I'm trying to install debathena from the installer scripts online, but
>>> during the installation, I'm asked to specify the fully qualified domain
>>> name I want to use for Postfix and other programs. (The default option
>>> appears to be "localhost.") What should I put here?
>>> I've tried to run the installer several times without success (after
>>> installation I'm never able to access my files in the AFS system or send
>>> Zephyrs, even after typing renew or kinit), so presumably I'm doing
>>> something wrong, which might have been guessing the wrong domain name to
>>> use here.
>>> Thank you for any help you can give me here.
>>> Best,
>>> Anthony
