# Linux Fundamentals CTF Flag Submission Issues

**URL:** <https://discuss.elastic.co/t/linux-fundamentals-ctf-flag-submission-issues/364276>\
**Category:** Elastic Training\
**Created:** [August 2, 2024, 2:15pm UTC](https://discuss.elastic.co/t/linux-fundamentals-ctf-flag-submission-issues/364276 "2024-08-02T14:15:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![drusse22](https://avatars.discourse-cdn.com/v4/letter/d/d26b3c/32.png) [@drusse22](https://discuss.elastic.co/u/drusse22)\
**Post date:** [August 2, 2024, 2:15pm UTC](https://discuss.elastic.co/t/linux-fundamentals-ctf-flag-submission-issues/364276/1 "2024-08-02T14:15:38Z")

</div>

Course: Linux Fundamentals  
Version: 56  
Question: I’ve recently been working my way through the Linux Fundamentals On Demand training course. I’ve found that in section 3. Searching and Filtering 3.B6 – BONUS – Commented lines 56 I am unable to input a correct submission…

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/a/f/af8c33888c9666970ad5c4d5d979fc7d8038bfdd.png)

[student@ip-172-31-11-113 ~]$ cd ~/searching/grep-ex/

[student@ip-172-31-11-113 grep-ex]$ pwd

/home/student/searching/grep-ex

[student@ip-172-31-11-113 grep-ex]$ ls

elasticsearch.yml secure.log

[student@ip-172-31-11-113 grep-ex]$ cat elasticsearch.yml

#Put this in: /etc/elasticsearch/elasticsearch.yml

# ======================== Elasticsearch Configuration =========================

# 

# NOTE: Elasticsearch comes with reasonable defaults for most settings.

# Before you set out to tweak and tune the configuration, make sure you

# understand what are you trying to accomplish and the consequences.

# 

# The primary way of configuring a node is via this file. This template lists

# the most important settings you may want to configure for a production cluster.

# 

# Please consult the documentation for further information on configuration options:

# [Elasticsearch Guide | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/index.html)

# 

# ---------------------------------- Cluster -----------------------------------

# 

# Use a descriptive name for your cluster:

# 

cluster.name: perched

# 

# ------------------------------------ Node ------------------------------------

# 

# Use a descriptive name for the node:

# 

node.name: UPDATE

# 

# Add custom attributes to the node:

# 

#node.attr.rack: r1

# 

# ----------------------------------- Paths ------------------------------------

# 

# Path to directory where to store the data (separate multiple locations by comma):

# 

path.data: UPDATE

# 

# Path to log files:

# 

path.logs: UPDATE

# 

# ----------------------------------- Memory -----------------------------------

# 

# Lock the memory on startup:

# 

bootstrap.memory\_lock: true

# 

# Make sure that the heap size is set to about half the memory available

# on the system and that the owner of the process is allowed to use this

# limit.

# 

# Elasticsearch performs poorly when the system is swapping the memory.

# 

# ---------------------------------- Network -----------------------------------

# 

# Set the bind address to a specific IP (IPv4 or IPv6):

# 

network.host: 172.16.1.100

# 

# Set a custom port for HTTP:

# 

http.port: UPDATE

# 

# For more information, consult the network module documentation.

# 

# --------------------------------- Discovery ----------------------------------

# 

# Pass an initial list of hosts to perform discovery when new node is started:

# The default list of hosts is ["127.0.0.1", "[::1]"]

# 

#discovery.zen.ping.unicast.hosts: ["host1", "host2"]

# 

# Prevent the "split brain" by configuring the majority of nodes (total number of master-eligible nodes / 2 + 1):

# 

#discovery.zen.minimum\_master\_nodes:

# 

# For more information, consult the zen discovery module documentation.

# 

# ---------------------------------- Gateway -----------------------------------

# 

# Block initial recovery after a full cluster restart until N nodes are started:

# 

#gateway.recover\_after\_nodes: 3

# 

# For more information, consult the gateway module documentation.

# 

# ---------------------------------- Various -----------------------------------

# 

# Require explicit names when deleting indices:

# 

#action.destructive\_requires\_name: true

[student@ip-172-31-11-113 grep-ex]$ grep -v "#" elasticsearch.yml

cluster.name: perched

node.name: UPDATE

path.data: UPDATE

path.logs: UPDATE

bootstrap.memory\_lock: true

network.host: 172.16.1.100

http.port: UPDATE

[student@ip-172-31-11-113 grep-ex]$

The submission box won't accept my answer of grep -v "#" elasticsearch.yml

What am I doing wrong? Any help would be appreciated!

---

<div class="post-metadata">

**Author:** ![drusse22](https://avatars.discourse-cdn.com/v4/letter/d/d26b3c/32.png) [@drusse22](https://discuss.elastic.co/u/drusse22)\
**Post date:** [August 5, 2024, 5:31pm UTC](https://discuss.elastic.co/t/linux-fundamentals-ctf-flag-submission-issues/364276/2 "2024-08-05T17:31:56Z")

</div>

Got the working answer of grep -v “^#” elasticsearch.yml Forgot to check for the space character at the beginning even though in this case it didn't change the output.